-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
[main] Update dependencies from dotnet/runtime #31178
[main] Update dependencies from dotnet/runtime #31178
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.
Auto-approving dependency update.
@dotnet/efteam there seems to be some issues here with failing tests. Can you take a look? |
Test failures look like something has changed in DI. |
@danmoseley Who do we reach out these days for regressions in the DI libraries? |
Microsoft.EntityFrameworkCore.DbContextTest.Resolve_scoped_application_service passes on Windows; fails on Linux and macOS with:
|
I think @dotnet/area-extensions-dependencyinjection should work |
Yeah whatever it says in https://github.com/dotnet/runtime/blob/main/docs/area-owners.md |
@dotnet/dnr-codeflow this one appears to be stalled |
@steveharter @mapogolions - was this failure caused by dotnet/runtime#87354? |
I'm not sure although that supposed to only affect cases when
This is suspect. Is it possible there is a threading or some other concurrency or cleanup issue affecting non-Windows, such as the use of |
@steveharter this definitely looks like a regression from changes in dotnet/runtime, are the failing unit tests not enough of a starting place? |
@ajcvickers @bricelam is the exceptional case being tested here an important result or can we open an issue and skip the test for now? runtime branches tomorrow for p7 so if this needs to escalate now is the time. |
it is failing on windows now too |
@lewing Yes this needs to escalate. Per policy, runtime needs to revert unless the fix can be made quickly. @danmoseley You asked me to ping you. |
@steveharter do we know what commit most likely caused this? Another option here would be to temporarily disable this one test to allow this to merge and file a release blocking bug to fix it. |
@ericstj Happy to disable a test once a release-blocking issue exists. |
I pulled out the test, ran it on dotnet/runtime@1815306...c06d77a This does seem to implicate dotnet/runtime@c06d77a |
I filed the issue and disabled the test. |
Seeing failures on mac and linux:
It looks to me like we're running new 8.0 assemblies on an older 8.0 runtime. |
@AndriySvyryd Aren't we were currently flowing the latest runtime bits as part of the AoT work? |
looks like that was fixed in #31270 |
That didn't fix it -- that might make it fail on Windows too. We need a newer SDK to get the updates to runtime. |
@bricelam thank you for jumping on this. Your change should fix #31300 To double check that we can look at the test logs. We expect them to be running against a framework version The framework version we don't expect is |
Confirmed. Test are running on |
Mac build is failing during build to run the compiler from the SDK - looks to me like it's using the wrong It's using
|
Yes, but #31284 was blocked on the same issue this is hitting:
|
I see, so we might need to undo the SDK update (since it's not needed now with @bricelam's changes) or figure out how to fix it. |
Looks like this path is coming from environment:
Comparing this to linux to see if that's the difference. |
There were some changes to how roslyn locates the dotnet to run the compiler etc. see Write guidance on how to launch (non apphost) apps · Issue #88754 · dotnet/runtime (github.com) & dotnet/roslyn#68918 / dotnet/roslyn#69010 |
Yep that's what did it: It's unusual that this Mac build is setting DOTNET_ROOT though -- I'm looking into why that is. The linux build doesn't set it. |
I don't think this repo is setting the DOTNET_ROOT value. I think it's already set on the build machine, it's just not overridden by the build process. |
Do other repos remove or override this during build normally? |
…0714.11 Microsoft.Extensions.Caching.Memory , Microsoft.Extensions.Configuration , Microsoft.Extensions.Configuration.Abstractions , Microsoft.Extensions.Configuration.EnvironmentVariables , Microsoft.Extensions.Configuration.Json , Microsoft.Extensions.DependencyInjection , Microsoft.Extensions.DependencyModel , Microsoft.Extensions.HostFactoryResolver.Sources , Microsoft.Extensions.Logging , System.Text.Json From Version 8.0.0-preview.7.23325.2 -> To Version 8.0.0-preview.7.23364.11
Filed dotnet/runtime#89109 to track this regression
a5a6476
to
bdc0998
Compare
I see -- dotnet/roslyn#69010 undid considering DOTNET_ROOT, but we must not yet have an SDK with that yet. We can undo the SDK change as @bricelam did until we get a new SDK with the revert. |
Unblocked. Thank you, everyone! |
This pull request updates the following dependencies
From https://github.com/dotnet/runtime