-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Fix nativeaot outerloop #108916
Fix nativeaot outerloop #108916
Conversation
/azp run runtime-nativeaot-outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
@carlossanlop this test was backported to both .NET 8 and .NET 9 and has been failing in outerloops ever since. We're about to ship .NET 9 GA with 16 out of 20 runtime-nativeaot-outerloop jobs consistently failing. I assume this means they are not part of our shipping criteria. Do you know how would I go about proposing adding runtime-nativeaot-outerloop to the shipping criteria? Cc @dotnet/ilc-contrib |
This doesn't fix all of outerloop because people were being productive writing more trim-unfriendly test code. I'll fix in a follow up in case we need to backport this PR. |
/backport to release/9.0 |
Started backporting to release/9.0: https://github.com/dotnet/runtime/actions/runs/11399867413 |
/backport to release/8.0 |
Started backporting to release/8.0: https://github.com/dotnet/runtime/actions/runs/11399872244 |
typeof(RegionInfo).Assembly.GetType
is too difficult to analyze for trimming. Native AOT outerloop runs crash with a NullReferenceException because the property is not reflection-visible.