Repository navigation
BlazorWasm AOT not requiring trimming #125233
Copy link
Copy link
Open
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarch-wasmWebAssembly architectureWebAssembly architecturearea-Build-mono
Milestone
Description
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1320866
Build error leg or test failing: Wasm.Build.Tests.Blazor.NativeTests.BlazorWasm_CannotAOT_WithNoTrimming(config: Release)
Pull request: #125193
Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": "AOT is not supported without IL trimming",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1320866
Error message validated: [AOT is not supported without IL trimming]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 3/5/2026 7:15:21 PM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 1 | 11 | 15 |
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarch-wasmWebAssembly architectureWebAssembly architecturearea-Build-mono
Activity
lewing commentedon Mar 7, 2026
Updated analysis (from binlog inspection)
My earlier analysis was incorrect about ILLink being involved. The binlog from the failing Helix run is truncated/corrupt — the MCP binlog tool reports:
This is the same
"Error when reading the fil..."string visible in the test output. The actual sequence:dotnet publishwithPublishTrimmed=false+RunAOTCompilation=trueEndOfStreamExceptionand emits that as the only error message"AOT is not supported without IL trimming"but only finds the file-reading errorThis is an infrastructure flake — OOM kill on Helix before the build reaches the
_WasmAotCompileApptarget where the validation error would be emitted. With only 1 hit/month, this seems consistent with sporadic memory pressure on Helix machines.dotnet-policy-service commentedon Jul 10, 2026
Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara
See info in area-owners.md if you want to be subscribed.