Repository navigation
wasi/test-wasi is flaky #59146
Description
Test
wasi/test-wasi
Platform
Other, Linux ARM64
Console output
(node:3240446) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
fd_write(2, 69600, 2, 69596)
Assertion failed: r == 0 (c/pthread.c: main: 17)
wasm://wasm/00020abe:1
RuntimeError: unreachable
at wasm://wasm/00020abe:wasm-function[26]:0x892
at wasm://wasm/00020abe:wasm-function[27]:0x8da
at wasm://wasm/00020abe:wasm-function[13]:0x46a
at wasm://wasm/00020abe:wasm-function[11]:0x328
at WASI.start (node:wasi:138:7)
at /home/iojs/build/workspace/node-test-commit-arm-debug/test/fixtures/wasi-preview-1.js:191:20Build links
See https://github.com/nodejs/reliability/blob/main/reports/2025-07-21.md
Additional information
This has failed 6 PRs out of the last 100 runs. It appears to be arm-debug only.
Activity
joyeecheung commentedon Jul 21, 2025
This round of the flake started from https://github.com/nodejs/reliability/blob/main/reports/2025-07-19.md but none of the referenced PR or PRs landed around that time look obviously related.
joyeecheung commentedon Aug 15, 2025
This is likely caused by #57214
github-actions commentedon Apr 19, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commentedon May 20, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 240 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
test: fix the thread-spawn handshake in the WASI threads fixture
test: ignore tunnel resets in proxy invalid-char-in-url test
test: do not dump core in external memory limit test
test: only count restarts after the write in watch emit-restarted test
test: fix the thread-spawn handshake in the WASI threads fixture
test: widen the gap in the resolver maxTimeout comparison
test: make node:bench test samples survive a coarse clock
test: ignore tunnel resets in proxy invalid-char-in-url test
10 remaining items
test: make node:bench test samples survive a coarse clock
test: ignore tunnel resets in proxy invalid-char-in-url test
test: only count restarts after the write in watch emit-restarted test
test: fix the thread-spawn handshake in the WASI threads fixture
test: widen the gap in the resolver maxTimeout comparison
test: ignore tunnel resets in proxy invalid-char-in-url test
test: only count restarts after the write in watch emit-restarted test
test: fix the thread-spawn handshake in the WASI threads fixture
test: widen the gap in the resolver maxTimeout comparison
test: ignore tunnel resets in proxy invalid-char-in-url test
test: only count restarts after the write in watch emit-restarted test
test: fix the thread-spawn handshake in the WASI threads fixture
test: widen the gap in the resolver maxTimeout comparison
test: do not dump core in external memory limit test
test: make node:bench test samples survive a coarse clock