Repository navigation
[wasi][coreclr] Library tests failing under aggressive trimming in the WASI R2R lane #135045
Description
Description
The CoreCLR WASI ReadyToRun library lane (LibraryTestsCoreCLR_WASI_R2R) builds the test apps with EnableAggressiveTrimming=true. A few suites fail there because trimming removes members that the tests only reach through reflection. Apple mobile (#91923) and browser hit the same problems and already quarantine these tests. They pass in the untrimmed WASI interpreter lane.
| Suite | Failures | Symptom |
|---|---|---|
| System.ComponentModel.Composition.Tests | 36 | MissingMethodException for ExportFactory<T> ctor, mscorlib FileNotFound, members not found by Expectations |
| Microsoft.Extensions.Configuration.Binder.Tests | 2 | TraceSwitchTest (Level stays Off), TestGraphWithUnsupportedMember |
Browser excludes System.ComponentModel.Composition.Tests entirely, and Apple mobile excludes it as unsupported. The two Binder tests carry ActiveIssue for Browser and for trimmed Apple mobile (#91923).
These are quarantined on WASI R2R (trimmed) in #134813.
Note
This issue was drafted with GitHub Copilot.
Activity
dotnet-policy-service commentedon Oct 1, 2026
Tagging subscribers to this area: @dotnet/crossgen-contrib
See info in area-owners.md if you want to be subscribed.
[wasi] Quarantine trimmed WASI R2R failures
[wasi] Quarantine trimmed WASI R2R failures
[wasi] Quarantine trimmed WASI R2R failures
[wasi] Implement MksTemps/MkdTemp so GetTempFileName and CreateTempSu…