-
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
Disable Aot and Trim analyzers when building runtime tests #88209
Conversation
When targeting native AOT, these analyzers are producing warnings that are treated as errors
Tagging subscribers to this area: @hoyosjs Issue DetailsWhen targeting native AOT, these analyzers are producing warnings that are treated as errors
|
@@ -129,6 +124,8 @@ | |||
<!-- Disable some C# warnings for the tests. --> | |||
<NoWarn>78,162,164,168,169,219,251,252,414,429,618,642,649,652,659,675,1691,1717,1718,3001,3002,3003,3005,3008,8981</NoWarn> | |||
<RunAnalyzers>false</RunAnalyzers> | |||
<EnableTrimAnalyzer>false</EnableTrimAnalyzer> |
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.
I have tried to disable it in more fine grained way first, but it turned out to be whack-a-mole.
This matches what we do for libraries 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.
We could condition on EnableAggressiveTrimming. Those should be clean
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.
They are not clean today. I agree it would be a good path to take if we wanted to spend time on incrementally enabling analyzers for test build.
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.
Thank you!
When targeting native AOT, these analyzers are producing warnings that are treated as errors