f845a16c58
Move the child process code into a fixture and split the test so that it can be run in parallel and it's easier to identify where the failure is coming from. Also use the spawnSyncAndExitWithoutError() utility so that the test shows complete information on failure. Instead of marking all the wasi tests as flaky, only mark the wasi-poll one which is flaking in the CI now. PR-URL: https://github.com/nodejs/node/pull/51836 Refs: https://github.com/nodejs/node/issues/51822 Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> |
||
|---|---|---|
| .. | ||
| c | ||
| wasm | ||
| Makefile | ||
| README.md | ||
| test-return-on-exit.js | ||
| test-wasi-exitcode.js | ||
| test-wasi-initialize-validation.js | ||
| test-wasi-io.js | ||
| test-wasi-not-started.js | ||
| test-wasi-options-validation.js | ||
| test-wasi-poll.js | ||
| test-wasi-start-validation.js | ||
| test-wasi-stdio.js | ||
| test-wasi-symlinks.js | ||
| test-wasi-worker-terminate.js | ||
| test-wasi.js | ||
| testcfg.py | ||
| wasi.status | ||
WASI Tests
Compile with clang and wasm32-wasi target by using the wasi-sdk
version 20
Install wasi-sdk and then set WASI_SDK_PATH to the root of the install.
You can then rebuild the wasm for the tests by running:
make CC=${WASI_SDK_PATH}/bin/clang SYSROOT=${WASI_SDK_PATH}/share/wasi-sysroot
If you update the version of the wasi-sdk to be used for the compile remove all of the *.wasm files in the wasm directory to ensure you rebuild/test all of the tests with the new version.