Spurious timeouts in CI
Michael-F-Bryan opened this issue Β· comments
Michael Bryan commented
It looks like a recent change has introduced some flakiness to our CI. The failure looks something like this:
tests/integration.test.ts:
π§ Browser logs:
An error was thrown in a Promise outside a test. Did you forget to await a function or assertion?
TypeError: Cannot read properties of undefined (reading 'read')
at X.n.wbg.__wbg_read_55c1f4e3f3729816 (dist/WasmerSDK.js:11:23485)
at http://localhost:8000/dist/wasmer_js_bg.wasm:wasm-function[850]:0x274ea9
at http://localhost:8000/dist/wasmer_js_bg.wasm:wasm-function[8[26](https://github.com/wasmerio/wasmer-js/actions/runs/7298041059/job/19888301266#step:13:27)]:0x26db88
at http://localhost:8000/dist/wasmer_js_bg.wasm:wasm-function[288]:0xc42f9
at http://localhost:8000/dist/wasmer_js_bg.wasm:wasm-function[1674]:0x320e56
at http://localhost:8000/dist/wasmer_js_bg.wasm:wasm-function[8636]:0x3f221d
at http://localhost:8000/dist/wasmer_js_bg.wasm:wasm-function[7881]:0x3ead01
at R (dist/WasmerSDK.js:11:[27](https://github.com/wasmerio/wasmer-js/actions/runs/7298041059/job/19888301266#step:13:28)93)
at i (dist/WasmerSDK.js:11:26[33](https://github.com/wasmerio/wasmer-js/actions/runs/7298041059/job/19888301266#step:13:34))
ERROR wasmer_js: panicked at src/utils.rs:57:22:
called `Result::unwrap()` on an `Err` value: JsValue(440)
β Wasmer.spawn > Can communicate with a TTY-aware program
Error: Timeout of 120000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
at createTimeoutError (node_modules/@web/test-runner-mocha/dist/autorun.js:1:191473)
at ds._timeoutError (node_modules/@web/test-runner-mocha/dist/autorun.js:1:195706)
at node_modules/@web/test-runner-mocha/dist/autorun.js:1:19[37](https://github.com/wasmerio/wasmer-js/actions/runs/7298041059/job/19888301266#step:13:38)87
Chrome: |ββββββββββββββββββββββββββββββ| 3/3 test files | 17 passed, 1 failed, 9 skipped
For example, I had to restart Compile and Test from the main CI job for #392 even though it only touches some config for an example (completely unrelated to Compile and Test).
This might also be related to SDK-37 where it looks like something is messing up wasm-bindgen
's bookkeeping, which means JsValue
s we think point at real objects are actually undefined
.
Linear commented