-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Remove workarounds #12812
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove workarounds #12812
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please double-check if anything else is closed and available in our current dependencies. E.g. anything else fixed in the preview 7 SDK?
<AppHostRuntimeIdentifiers /> | ||
</KnownFrameworkReference> | ||
</ItemGroup> | ||
|
||
<!-- Work around https://github.com/dotnet/cli/issues/11378. --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove this bit as well. This old workaround is not necessary now that we're using the preview 7 SDK. The last few comments about a new problem in the preview 8 SDK are worked around above
|
I've investigated this a little more and it seems like the workaround we want to remove for https://github.com/dotnet/cli/issues/11378 still affects building some projects for reference assemblies: I'm not sure why this only seems to affect some (but not all) reference assembly projects but it seems like we can't remove the workaround just yet. This only seem to affect windows builds only and no other platforms. @dsplaisted would you know what to look for here? FYI, the binlogs that I'm looking at is here: https://dev.azure.com/dnceng/public/_build/results?buildId=292612&view=logs&jobId=d9e61dd5-50da-562f-684c-804952f2640b. For the time being, I'm adding back the workarounds. |
@dsplaisted as @JunTaoLuo described, we're still seeing
if we remove the dotnet/cli#11378 workaround (a conditional With the 3.0.100-preview7-012821 .NET SDK, shouldn't we have picked up the bug fix? Or, is the problem only fixed on CI agents with VS 16.2 or later (for example)? If this is relevant, the errors are visible with both BuildPool.Windows.10.Amd64.VS2019.BT.Open and BuildPool.Windows.10.Amd64.VS2019.Open agents. (Not positive what VS 2019 version those agents have installed at the moment.) |
@JunTaoLuo suggest getting this in and leaving #11701 as well as any improvements related to dotnet/cli#11378 for later. Your build was clean 😃 |
Missing an approval but I can rage merge 😄 |
Following up to #12557. I'll send a tell-mode email if this PR passes.