Uh oh!
There was an error while loading. Please reload this page.
Fix some tests regressed by the aggressive reflection metadata trimming work - #71440
Conversation
LakshanF
commented
Jun 29, 2022
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
MichalStrehovsky
left a comment
There was a problem hiding this comment.
Looks good!
Could you please file an issue to get rid of the IlcTrimMetadata (and add a link to the issue from each of the CSPROJ)? IlcTrimMetadata is not a shipping configuration and I would like us to test the shipping configuration.
Basically, if the test is failing because the test itself is doing some unanalyzable reflection that targets the framework, we should either make the test analyzable, or add RD.XML. If the test is failing because the framework itself is doing some reflection, that's potentially a product bug that we would want to look at in detail.
We test IlcTrimMetadata in a targeted test under src/test/nativeaot.
LakshanF
commented
Jun 30, 2022
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
The aggressive reflection trimming PR, #70201 regressed some library tests and that PR just missed the RR enabling effort that came soon after (so the regressions couldn't be caught at that time). Getting these tests to pass again by setting
IlcTrimMetadatato false.There are some other tests that require a deeper investigation since the error message looks puzzling at first glance,