Repository navigation
flaky: wasi.test-wasi #51822
Description
Test
wasi/test-wasi
Platform
Windows
Console output
06:42:50 node:assert:126
06:42:50 throw new AssertionError(obj);
06:42:50 ^
06:42:50
06:42:50 AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
06:42:50
06:42:50 3221225477 !== 0
06:42:50
06:42:50 at innerRunWASI (d:\workspace\node-test-binary-windows-js-suites\node\test\wasi\test-wasi.js:80:12)
06:42:50 at runWASI (d:\workspace\node-test-binary-windows-js-suites\node\test\wasi\test-wasi.js:86:5)
06:42:50 at Object.<anonymous> (d:\workspace\node-test-binary-windows-js-suites\node\test\wasi\test-wasi.js:111:3)
06:42:50 at Module._compile (node:internal/modules/cjs/loader:1368:14)
06:42:50 at Module._extensions..js (node:internal/modules/cjs/loader:1426:10)
06:42:50 at Module.load (node:internal/modules/cjs/loader:1205:32)
06:42:50 at Module._load (node:internal/modules/cjs/loader:1021:12)
06:42:50 at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:142:12)
06:42:50 at node:internal/main/run_main_module:28:49 {
06:42:50 generatedMessage: true,
06:42:50 code: 'ERR_ASSERTION',
06:42:50 actual: 3221225477,
06:42:50 expected: 0,
06:42:50 operator: 'strictEqual'
06:42:50 }
06:42:50
06:42:50 Node.js v22.0.0-preBuild links
Additional information
@nodejs/wasi
Activity
[-]falky: wasi/test-wasi is flaky[/-][+]falky: wasi.test-wasi[/+][-]falky: wasi.test-wasi[/-][+]flaky: wasi.test-wasi[/+]targos commentedon Feb 21, 2024
3221225477is0xC000005(Access Violation). I think this is equivalent to a segmentation fault so there's a real bug somewhere.@nodejs/platform-windows.
joyeecheung commentedon Feb 22, 2024
I tried resuming Windows a few times lately and all of them failed because of this error on Windows + ARM - and it's almost constantly failing as far as I can tell from CI history. I think we should mark it as flaky for Windows + ARM for now. On a side note it would be easier to debug the test if it's split instead of putting all the test cases together in one file.
joyeecheung commentedon Feb 22, 2024
Maybe someone from @nodejs/wasi is up for splitting that test? It seems that could be rewritten with custom configuration in python instead, which would also help making the test run faster by running the test cases in parallel (currently it takes 3.7s to run on a beefy laptop, in the CI on Windows this takes ~15s)
test: mark test-wasi as flaky on Windows on ARM
joyeecheung commentedon Feb 22, 2024
#51836 shows that only the test case of
poll()is flaking.test: split wasi tests
test: mark test-wasi as flaky on Windows on ARM
test: split wasi tests
test: mark test-wasi as flaky on Windows on ARM
test: split wasi tests
test: mark test-wasi as flaky on Windows on ARM
test: split wasi poll test for windows
test: split wasi poll test for windows
test: split wasi poll test for windows
test: split wasi poll test for windows