-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[master] Update dependencies from mono/linker #15955
[master] Update dependencies from mono/linker #15955
Conversation
Microsoft.NET.ILLink.Analyzers , Microsoft.NET.ILLink.Tasks From Version 6.0.100-preview.2.21118.1 -> To Version 6.0.100-preview.2.21118.3
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
Microsoft.NET.ILLink.Analyzers , Microsoft.NET.ILLink.Tasks From Version 6.0.100-preview.2.21118.1 -> To Version 6.0.100-preview.2.21118.4
Microsoft.NET.ILLink.Analyzers , Microsoft.NET.ILLink.Tasks From Version 6.0.100-preview.2.21118.1 -> To Version 6.0.100-preview.2.21122.1
Using the same property that suppresses the linker warnings. Includes a manual dependency update to unblock dotnet#15955.
Using the same property that suppresses the linker warnings. Includes a manual dependency update to unblock dotnet#15955.
@ViktorHofer there seem to be several failures caused by the linker target change. Could you look into that or should we revert your change? |
Yes, will take a look |
Microsoft.NET.ILLink.Analyzers , Microsoft.NET.ILLink.Tasks From Version 6.0.100-preview.2.21118.1 -> To Version 6.0.100-preview.2.21124.1
Looks like there are new test failures now, e.g.
|
Microsoft.NET.ILLink.Analyzers , Microsoft.NET.ILLink.Tasks From Version 6.0.100-preview.2.21118.1 -> To Version 6.0.100-preview.2.21124.2
Microsoft.NET.ILLink.Analyzers , Microsoft.NET.ILLink.Tasks From Version 6.0.100-preview.2.21118.1 -> To Version 6.0.100-preview.2.21124.3
Are those failures related to the linker changes? |
Those failures should be addressed by #16021. (Yes, they are because we started getting additional warnings from the linker Roslyn analyzer with dotnet/linker#1844) |
@sbomer could you commit relevant NotHaveStdOutContaining fixes to this PR so we can merge it before 16201 ? |
@marek-safar I don't think we should take the update without 16021 because it breaks the scenario tests are validating (that these warnings are suppressed by default). It also looks like the I need to make one more test fix for the windows legs - so it might be faster to get the update in as part of 16021 anyway. If I get blocking feedback on that change and we really need it now, I can temporarily disable the failing tests here to unblock it. |
@sbomer you could disable the tests temporary too |
I'll disable the tests if #16021 doesn't go in by EOD |
* Suppress illink roslyn analyzer warnings Using the same property that suppresses the linker warnings. Includes a manual dependency update to unblock #15955. * Update package * Fix test failures on desktop MSBuild - Filter for more specific log messages. Otherwise the MSBuild output which for some reason is more verbose on Windows will contain the string IL2026. - Work around issues passing semicolon-delimited properties as command-line arguments.
Using the same property that suppresses the linker warnings. Includes a manual dependency update to unblock dotnet#15955.
This pull request updates the following dependencies
From https://github.com/mono/linker