[wasm][tests] Tracking issue for test failures with AOT

[radical]

This is for tracking test failures when running with AOT.

• The main PR for this work is Shift Most of Wasm AOT test build to helix #48226

• And a follow up PR ([wasm] Fix trimming errors for library tests, to help building with AOT #50885) has various fixes for the EAT issues

  • this adds a build for EAT (and AOT) under runtime-staging

• These tests are built with /p:RunAOTCompilation=true /p:EnableAggressiveTrimming=true (AOT+EAT)

  • the EAT part can introduce issues, compared to a regular test build
  • But all those are either disabled, or fixed in the second PR

• With the issues for just EAT, fixed, the AOT build should have only the AOT test failures

• the issues are labeled wasm-aot-test

To reproduce locally:

1. use the branch from the second PR
2. $ /dotnet.sh build /p:Configuration=Release /p:TargetOS=Browser /p:TargetArchitecture=wasm /t:Test /path/to/project/file /p:EnableAggressiveTrimming=true /p:RunAOTCompilation=true
3. If you are not able to reproduce it with the above, then try building with /p:BuildAOTTestsOnHelix=true to the above command line
4. 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
• Add /p:WasmNativeDebugSymbols=true /p:WasmNativeStrip=false for better traces
• You can try /p:_WasmDevel=true for improving the build times (a bit)
• It can be useful to run the tests in a browser. For that:
  • WasmXHarnessArgs="--no-headless --no-quit" Scenario=WasmTestOnBrowser - this will launch chrome in "headed" mode, and it won't quit after the tests are done
  • And adding WasmXHarnessMonoArgs="--runtime-arg=--trace=E" - will get you extra traces, but with v8 you will only see Native stacktrace (mono_llvm_cpp_throw_exception), but in the browser's js console, you can see the full trace for that

Name	Issue	crash/build-error
System.IO.Pipelines	#50959	n
System.Runtime.Extensions.Tests	#51676	n
System.Runtime.Serialization.Xml.ReflectionOnly.Tests	#51679	n
System.Runtime.Tests	#52393	n
System.Text.Json.Tests	#51961	y

Tests that were failing till very recently

Name	Issue	crash/build-error
System.Reflection.Tests	#51673	n
System.Runtime.Loader.DefaultContext.Tests	#51680	y
System.Runtime.Loader.Tests	#51678	n
System.Text.Encodings.Web.Tests	#50965	y
System.CodeDom.Tests	#51723	y

(not an exhaustive list. See label wasm-aot-test for all the issues)

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

Issue Details

---

This is for tracking test failures when running with AOT.

• The main PR for this work is Shift Most of Wasm AOT test build to helix #48226

• And a follow up PR ([wasm] Fix trimming errors for library tests, to help building with AOT #50885) has various fixes for the EAT issues

  • this adds a build for EAT (and AOT) under runtime-staging

• These tests are built with /p:RunAOTCompilation=true /p:EnableAggressiveTrimming=true (AOT+EAT)

  • the EAT part can introduce issues, compared to a regular test build
  • But all those are either disabled, or fixed in the second PR

• With the issues for just EAT, fixed, the AOT build should have only the AOT test failures

• the issues are labeled wasm-aot-test

To reproduce locally:

1. use the branch from the second PR
2. $ /dotnet.sh build /p:Configuration=Release /p:TargetOS=Browser /p:TargetArchitecture=wasm /t:Test /path/to/project/file /p:EnableAggressiveTrimming=true /p:RunAOTCompilation=true
3. If you are not able to reproduce it with the above, then try building with /p:BuildAOTTestsOnHelix=true to the above command line
4. 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
• Add /p:WasmNativeDebugSymbols=true /p:WasmNativeStrip=false for better traces
• You can try /p:_WasmDevel=true for improving the build times (a bit)

Author:	radical
Assignees:	-
Labels:	arch-wasm, area-Codegen-AOT-mono, wasm-aot-test
Milestone:	-

[radical]

cc @steveisok @mdh1418 @vargaz @SamMonoRT @naricc

[SamMonoRT]

cc @fanyang-mono

[SamMonoRT]

@radical @lewing - any more work left for this tracking issue ?