[8.0][wasm] `NodeJS` engine fails with `experimental-wasm-simd` and `experimental-wasm-eh` exit code: 9 -> exit code: 71 (GENERAL_FAILURE)
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=925493
Build error leg or test failing: Wasm.Build.Tests.HybridGlobalizationTests.AOT_HybridGlobalizationTests in net8.0-browser-Release-wasm-Mono_Release_linux-BuildWasmApps-(Ubuntu.2204.Amd64)Ubuntu.2204.Amd64.Open
Error Message
{
"ErrorMessage" : "[wasm test] XHarness exit code: 71 (GENERAL_FAILURE)",
"BuildRetry" : false,
"ExcludeConsoleLog" : false
}
- PR: https://github.com/dotnet/runtime/pull/111421
- Logs and artifacts: https://dev.azure.com/dnceng-public/public/_build/results?buildId=925493&view=ms.vss-test-web.build-test-results-tab&runId=24494878&resultId=100031&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab
- Log file: https://helixr1107v0xd1eu3ibi6ka.blob.core.windows.net/dotnet-runtime-refs-pull-111421-merge-0fa1ca5cd587484183/Workloads-Wasm.Build.Tests.HybridGlobalizationTests/1/console.aa154e60.log?helixlogtype=result
- Output:
[wasm test] With env vars:
[wasm test] LANG = 'en-US'
[wasm test]
[wasm test] [19:07:22] info: Process node exited with 9
[wasm test]
[wasm test] [19:07:22] info: Waiting to flush log messages with a timeout of 120 secs ..
[wasm test] [19:07:22] info: /usr/bin/node: bad option: --experimental-wasm-simd
[wasm test] [19:07:22] info: /usr/bin/node: bad option: --experimental-wasm-eh
[wasm test] [19:07:22] fail: Application has finished with exit code 9 but 42 was expected
[wasm test] [19:07:22] dbug: Saving diagnostics data to '/root/helix/work/workitem/e/diagnostics.json'
[wasm test] XHarness exit code: 71 (GENERAL_FAILURE)
Exit code: 71
Known issue validation
Build: :mag_right: https://dev.azure.com/dnceng-public/public/_build/results?buildId=925493
Error message validated: [[wasm test] XHarness exit code: 71 (GENERAL_FAILURE)]
Result validation: :white_check_mark: Known issue matched with the provided build.
Validation performed at: 1/23/2025 5:46:01 PM UTC
Report
| Build | Definition | Test | Pull Request |
|---|---|---|---|
| 1063997 | dotnet/runtime | Workloads-NoWebcil-ST-Wasm.Build.Tests.WasmBuildAppTest.WorkItemExecution | dotnet/runtime#115596 |
| 1063280 | dotnet/runtime | Workloads-NoWebcil-ST-Wasm.Build.Tests.WasmBuildAppTest.WorkItemExecution | dotnet/runtime#116459 |
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 2 | 2 |
Tagging subscribers to 'arch-wasm': @lewing See info in area-owners.md if you want to be subscribed.
Tagging subscribers to this area: @akoeplinger, @matouskozak See info in area-owners.md if you want to be subscribed.
This is not HybridGlobalization related failure but NodeJS related. It complains about passing -engine-arg=--experimental-wasm-simd --engine-arg=--experimental-wasm-eh in WBT.
Should get fixed by https://github.com/dotnet/runtime/pull/111655 (8.0 was hit only once, all the other failures are 9.0)
The most recent failures are coming from 9.0 branch where the changes didn't land yet (there are in 9.0-staging)
maybe we can just disable NodeJS legs
maybe we can just disable NodeJS legs
That's done, isn't it? https://github.com/dotnet/runtime/pull/108582
I mean in Net9 Net8 branches
maybe we can just disable NodeJS legs
https://github.com/dotnet/runtime/pull/120195 https://github.com/dotnet/runtime/pull/120193