Fix or disable wasm64-emscripten-windows-chrome
Wasm64, as a platform is experimental in all wasm runtimes and even in LLVM.
The new wasm64-emscripten-windows-chrome
test job introduced in !11099 (merged) does not seem to launch chrome with --experimental-wasm-memory64
even when the flag is present in --engine-args
. However, when the test suite is run manually inside powershell from the dashboard runner (through metaverse), it works correctly. This needs investigating.
Job:
https://gitlab.kitware.com/vtk/vtk/-/jobs/9787599
Log:
Test #987: VTK::RenderingCoreCxx-TestBackfaceCulling ....................................................***Failed 5.37 sec
2024-05-23 17:19:31,356 Serving HTTP at http://127.0.0.1:64411/
2024-05-23 17:19:31,357 Running subprocess 'C:/glr/builds/vtk/vtk-ci-ext/0/.gitlab/chrome/chrome.exe --disable-restore-session-state --no-default-browser-check --no-first-run --incognito --disable-application-cache --new-tab --js-flags=--experimental-wasm-memory64 http://127.0.0.1:64411/'
2024-05-23 17:19:36,472 wasm streaming compile failed: CompileError: WebAssembly.instantiateStreaming(): invalid memory limits flags 0x7 (enable via --experimental-wasm-memory64) @+5489
falling back to ArrayBuffer instantiation
failed to asynchronously prepare wasm: CompileError: WebAssembly.instantiate(): invalid memory limits flags 0x7 (enable via --experimental-wasm-memory64) @+5489
Aborted(CompileError: WebAssembly.instantiate(): invalid memory limits flags 0x7 (enable via --experimental-wasm-memory64) @+5489)
Uncaught rejection from [object Promise]: RuntimeError: Aborted(CompileError: WebAssembly.instantiate(): invalid memory limits flags 0x7 (enable via --experimental-wasm-memory64) @+5489). Build with -sASSERTIONS for more info.
2024-05-23 17:19:36,484 Received exit code 1