-
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
Run DependencyInjection trimming tests as native AOT. #101129
Conversation
Tagging subscribers to this area: @dotnet/area-extensions-dependencyinjection |
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
|
||
<ItemGroup> | ||
<TestConsoleAppSourceFiles Include="..\TrimmingTests\ActivatorUtilitiesTests.cs" /> | ||
<TestConsoleAppSourceFiles Include="..\TrimmingTests\ServiceCollectionExtensionsTests.cs" /> |
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.
What's the key by which we decide the trimming tests that should be also native AOT tests?
ServiceCollectionExtensionsTests would not have hit the issue we were discussing and feels as applicable as any other trimming test.
Should we just run all trimming tests? There's a greater than zero chance they may catch something and it only makes the CI a couple minutes slower.
These tests are testing assumptions under which we suppressed static analysis warnings. We've made the wrong call on suppressing a warning many times in the past. There could be an AOT angle to the trimming suppression. I think that might tip the scale to "all TrimmingTests should be AOT tests".
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.
Should we just run all trimming tests?
Yes, I think that would be a good idea. I don't have time to do it myself right now, so it would be great if someone else could pick that up.
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.
Should we just run all trimming tests?
Yes, I think that would be a good idea. I don't have time to do it myself right now, so it would be great if someone else could pick that up.
Seemed straightforward enough so I just did it in #101229. Looks like it found stuff. Unclear if test issues or product issues at this point.
This will not run the legs that execute the added tests. I think you need |
/azp run runtime-nativeaot-outerloop |
Still didn't trigger the legs. The AOT library tests are conditioned on the build being Release, but we only do that in the tests that run when you change native AOT. outerloop CoreCLR pri-0 tests (where this is hooked into) is checked only |
Seems like we should fix that. How else are you supposed to exercise the tests when you change just the tests? |
That's a consequence of how native AOT app testing was hooked up in #76109. It runs with src/tests test execution ("CoreCLR testing") and also filters itself to release builds only. We either find a better home for this step (somewhere with libs testing), or at least remove the Release only filter. runtime/eng/pipelines/coreclr/nativeaot-post-build-steps.yml Lines 10 to 31 in 56510f0
|
Closing in favor of #101229 which will run all trimming tests with |
See #101031 (comment)