Flaky test TestRun/panic_fails in Windows
Opened this issue · 3 comments
agnivade commented
=== RUN TestRun/panic_fails
=== PAUSE TestRun/panic_fails
=== RUN TestRun/panic_in_next_run_of_event_loop_fails
=== PAUSE TestRun/panic_in_next_run_of_event_loop_fails
=== CONT TestRun/panic_in_next_run_of_event_loop_fails
=== CONT TestRun/panic_fails
main_test.go:73: Unexpected error message: "exit with status 2" != "websocket url timeout reached"
=== NAME TestRun/panic_in_next_run_of_event_loop_fails
main_test.go:73: Unexpected error message: "context canceled" != "websocket url timeout reached"
--- FAIL: TestRun (0.00s)
--- FAIL: TestRun/panic_fails (24.93s)
--- FAIL: TestRun/panic_in_next_run_of_event_loop_fails (24.93s)
hajimehoshi commented
We have a very similar issue hajimehoshi/ebiten#2982
hajimehoshi commented
https://pkg.go.dev/github.com/chromedp/chromedp#WSURLReadTimeout
Would it be possible to adjust the timeout?
agnivade commented
Hmm .. the default value seems 20 seconds which should be more than enough. I could increase it, but it would just push the goal post. I wonder if there's a deeper problem here.