Skip to content

BlazorWasm AOT not requiring trimming #125233

Open

Description

@agocke

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

Build Repository Test Pull Request
1651155 dotnet/runtime Wasm.Build.Tests.Blazor.NativeTests.BlazorWasm_CannotAOT_WithNoTrimming
1650601 dotnet/runtime Wasm.Build.Tests.Blazor.NativeTests.BlazorWasm_CannotAOT_WithNoTrimming
1650108 dotnet/runtime Wasm.Build.Tests.Blazor.NativeTests.BlazorWasm_CannotAOT_WithNoTrimming
1649817 dotnet/runtime Wasm.Build.Tests.Blazor.NativeTests.BlazorWasm_CannotAOT_WithNoTrimming
1647851 dotnet/runtime Wasm.Build.Tests.NativeBuildTests.AOTNotSupportedWithNoTrimming(config: Release, aot: True) #136381
1647292 dotnet/runtime Wasm.Build.Tests.Blazor.NativeTests.BlazorWasm_CannotAOT_WithNoTrimming #136382
1646146 dotnet/runtime Wasm.Build.Tests.Blazor.NativeTests.BlazorWasm_CannotAOT_WithNoTrimming #136338
1646093 dotnet/runtime Wasm.Build.Tests.Blazor.NativeTests.BlazorWasm_CannotAOT_WithNoTrimming
1645212 dotnet/runtime Wasm.Build.Tests.Blazor.NativeTests.BlazorWasm_CannotAOT_WithNoTrimming #136229
1644726 dotnet/runtime Wasm.Build.Tests.Blazor.NativeTests.BlazorWasm_CannotAOT_WithNoTrimming #136229
1644109 dotnet/runtime Wasm.Build.Tests.Blazor.NativeTests.BlazorWasm_CannotAOT_WithNoTrimming #136229
1640185 dotnet/runtime Wasm.Build.Tests.NativeBuildTests.IntermediateBitcodeToObjectFilesAreNotLLVMIR #136074
1625704 dotnet/runtime Wasm.Build.Tests.NativeBuildTests.IntermediateBitcodeToObjectFilesAreNotLLVMIR(config: Release, aot: True) #134158
1620556 dotnet/runtime Wasm.Build.Tests.NativeBuildTests.IntermediateBitcodeToObjectFilesAreNotLLVMIR(config: Release, aot: True) #134158
1618527 dotnet/runtime Wasm.Build.Tests.NativeBuildTests.SimpleNativeBuild(config: Release, aot: False) #134158

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
1 11 15

Activity

  1. added
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    Known Build ErrorUse this to report build issues in the .NET Helix tab
    on Mar 5, 2026
  2. removed
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    on Mar 7, 2026
  3. lewing commented on Mar 7, 2026

    @lewing
    Member

    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:

    Error when reading the file: System.IO.EndOfStreamException: Unable to read beyond the end of the stream.
    

    This is the same "Error when reading the fil..." string visible in the test output. The actual sequence:

    1. Test runs dotnet publish with PublishTrimmed=false + RunAOTCompilation=true
    2. The dotnet process gets killed mid-build on Helix (the other test in the same work item got exit code 137 = SIGKILL/OOM)
    3. The binlog is left truncated on disk
    4. The test infrastructure sees no "Build failed" in stdout, falls back to parsing the binlog
    5. The binlog reader hits EndOfStreamException and emits that as the only error message
    6. The test asserts on "AOT is not supported without IL trimming" but only finds the file-reading error

    This is an infrastructure flake — OOM kill on Helix before the build reaches the _WasmAotCompileApp target where the validation error would be emitted. With only 1 hit/month, this seems consistent with sporadic memory pressure on Helix machines.

  4. removed
    untriagedNew issue has not been triaged by the area owner
    on Mar 31, 2026
  5. dotnet-policy-service commented on Jul 10, 2026

    @dotnet-policy-service
    Contributor

    Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara
    See info in area-owners.md if you want to be subscribed.

  6. added this to the 12.0.0 milestone on Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions