-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Baseline new warning in trimming tests #114424
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
ToolsTests legs are failing: #114406 (comment) Psychic debugging (without actually trying to repro anything) tells me this is from #114346 that makes us emit more dynamic keyword warnings. That PR didn't trigger the ToolsTests leg since it's not a ILLink change.
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.
Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (1)
src/tools/illink/test/Mono.Linker.Tests.Cases/DataFlow/DynamicObjects.cs:132
- Consider adding a comment to clarify that the duplicate ExpectedWarning attribute is intentional, ensuring that future maintainers understand it reflects the new baseline for dynamic keyword warnings.
[ExpectedWarning ("IL3050", Tool.NativeAot, "https://github.com/dotnet/runtime/issues/94427")]
|
Tagging subscribers to this area: @dotnet/illink |
|
/ba-g timeout in unrelated leg |
ToolsTests legs are failing: #114406 (comment)
Psychic debugging (without actually trying to repro anything) tells me this is from #114346 that makes us emit more dynamic keyword warnings. That PR didn't trigger the ToolsTests leg since it's not a ILLink change.
Fix #114426