-
Notifications
You must be signed in to change notification settings - Fork 5.3k
[release/5.0] Update to latest .NET 5 SDK #59428
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
Conversation
|
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue Detailsnull
|
|
@danmoseley @jeffschwMSFT Required to unblock 5.0 builds. |
|
@jeffschwMSFT Interesting test failures? |
|
It is 1 test failure that is failing consistently across these runs. @agocke / @mateoatr can y'all take a look at this 5.0 test failure? |
|
Looking -- unfortunately it seems to have passed locally for me, so I'll need to investigate more |
|
@agocke Should I merge this to unblock 5.0 or is this worrying enough to warrant holding off 5.0 for? |
|
I can repro and I'm looking why this started happening; not seeing anything obvious. Based on the csproj of the failing test, it looks like the assemblies are not being put in the expected location. |
So this looks like a test issue? |
|
Building on Matt's comment. If we feel this is a regression, what is the likely impact? Since this is the SDK to build the product, do we have this pattern and this is a guard against a later/subtle failure. If we feel this has a low impact, we can disable and unblock this dependency flow and continue to investigate. |
|
It also looks like it only happens in checked builds. We could probably disable the test for now while we investigate |
No description provided.