-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Unset repo tools manifest path in CI to fix restore errors #33871
Conversation
a100946
to
af575b3
Compare
eng/Tools.props
Outdated
@@ -2,6 +2,9 @@ | |||
<PropertyGroup> | |||
<MSBuildTreatWarningsAsErrors>false</MSBuildTreatWarningsAsErrors> | |||
<EnableAnalyzers>true</EnableAnalyzers> | |||
<!-- Unset the repo tool manifest property in CI as we don't use repo tools there anyway, | |||
until https://github.com/dotnet/sdk/issues/10938 is fixed. --> | |||
<_RepoToolManifest /> |
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.
The comment says in CI
, however, this operation is not conditioned to CI.
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.
Thanks, lol fixed.
An updated SDK with the net5.0 tfm change seems to break dotnet repo tool restore, presumably because multiple compatible tfms are found. Working around this by deleting the repo tools manifest file until the issue is fixed.
af575b3
to
337576f
Compare
Here's the official build: https://dnceng.visualstudio.com/internal/_build/results?buildId=567300 |
cc @dotnet/dnceng |
@dotnet/runtime-infrastructure Feel free to merge after CI has completed. I believe the current failures are all unrelated. I'm logging off now but can take a look tomorrow if the PR isn't merged by then. |
An updated SDK with the net5.0 tfm change seems to break dotnet repo
tool restore, presumably because multiple compatible tfms are found.
Working around this by unsetting the repo tools manifest file path until the
issue is fixed.
Fixes #33837
cc @stephentoub