Skip to content

[wasm][tests] Tracking issue for errors with EnableAggressiveTrimming, for building AOT tests #51249

@radical

Description

@radical

To enable running tests with AOT, we need to use $(EnableAggressiveTrimming)==true, to reduce the AOT build time. Enabling this introduces some build issues, or test failures though.

To reproduce locally:

  1. $ /dotnet.sh build /p:Configuration=Release /p:TargetOS=Browser /p:TargetArchitecture=wasm /t:Test /path/to/project/file /p:EnableAggressiveTrimming=true
  2. If you are not able to reproduce it with the above, then try building with /p:BuildAOTTestsOnHelix=true to the above command line
  3. If you still cannot reproduce, then ask on the discord channel, as it might be a helix issue

tips:

  • make sure to assign the issue to yourself, if you are working on it
  • You can add /p:DebuggerSupport=true to get line numbers

Metadata

Metadata

Assignees

No one assigned

    Labels

    arch-wasmWebAssembly architecturearea-Build-monotrackingThis issue is tracking the completion of other related issues.trimming-for-aot`EnableAggressiveTrimming=true` used for running tests with AOT

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions