wasmbrowsertest: wasmbrowsertest taking too long and not printing any output
https://travis-ci.com/nhooyr/websocket/jobs/288703981
--- FAIL: TestWasm (60.00s)
conn_test.go:305: wasm test binary failed: signal: killed:
This is indicating the go test -exec=wasmbrowsertest
command failed as it was killed by the 60s timeout.
travis config: https://github.com/nhooyr/websocket/blob/5afbe3c1d163117b5ff9df021aa4b14e6ab2e7b5/.travis.yml#L25-L31
go test
invocation: https://github.com/nhooyr/websocket/blob/wasm/conn_test.go#L300-L307
wasm test: https://github.com/nhooyr/websocket/blob/5afbe3c1d163117b5ff9df021aa4b14e6ab2e7b5/ws_js_test.go
As you can see, even with the t.Fatal in the wasm test, wasmbrowsertest
is timing out after 60s and prints no output. Any ideas why?
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 39 (13 by maintainers)
Commits related to this issue
- Back to GH Actions See https://github.com/agnivade/wasmbrowsertest/issues/15 — committed to nhooyr/websocket by nhooyr 4 years ago
- Back to GH Actions See https://github.com/agnivade/wasmbrowsertest/issues/15 — committed to nhooyr/websocket by nhooyr 4 years ago
- Back to GH Actions See https://github.com/agnivade/wasmbrowsertest/issues/15 — committed to nhooyr/websocket by nhooyr 4 years ago
- Back to GH Actions See https://github.com/agnivade/wasmbrowsertest/issues/15 — committed to nhooyr/websocket by nhooyr 4 years ago
- Back to GH Actions See https://github.com/agnivade/wasmbrowsertest/issues/15 — committed to nhooyr/websocket by nhooyr 4 years ago
- Back to GH Actions See https://github.com/agnivade/wasmbrowsertest/issues/15 — committed to nhooyr/websocket by nhooyr 4 years ago
- Back to GH Actions See https://github.com/agnivade/wasmbrowsertest/issues/15 — committed to nhooyr/websocket by nhooyr 4 years ago
- Back to GH Actions See https://github.com/agnivade/wasmbrowsertest/issues/15 — committed to nhooyr/websocket by nhooyr 4 years ago
- Back to GH Actions See https://github.com/agnivade/wasmbrowsertest/issues/15 — committed to nhooyr/websocket by nhooyr 4 years ago
- Back to GH Actions See https://github.com/agnivade/wasmbrowsertest/issues/15 — committed to nhooyr/websocket by nhooyr 4 years ago
- Back to GH Actions See https://github.com/agnivade/wasmbrowsertest/issues/15 — committed to nhooyr/websocket by nhooyr 4 years ago
- Back to GH Actions See https://github.com/agnivade/wasmbrowsertest/issues/15 — committed to nhooyr/websocket by nhooyr 4 years ago
I plan to take a look some time. I will keep this open for now.
I cloned your repo locally. It seems like your tests itself were incorrect.
Are you sure you tested this locally before running in CI ? š
Here is the diff which fixes it. Let me know if you still see problems.