Flaky test TestRun/panic_fails in Windows

[agnivade]

=== 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]

We have a very similar issue hajimehoshi/ebiten#2982

[hajimehoshi]

https://pkg.go.dev/github.com/chromedp/chromedp#WSURLReadTimeout

Would it be possible to adjust the timeout?

[agnivade]

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.

[agnivade]

Re-ran tests multiple times with the associated PR. Looks like the problem is gone now.

[agnivade]

Well, no. It fails in master. Reopening, and skipping the test on Windows for now.

[hajimehoshi]

Apparently the issue was resolved. Thank you very much!

[hajimehoshi]

This still happens on Linux https://github.com/hajimehoshi/ebiten/actions/runs/10322461269/job/28577724123

[agnivade]

Go 1.19 is quite old. I am not 100% if that plays any role or not, but I only test with supported Go releases.

[hajimehoshi]

Sure, I'll let you know when the same thing happens with the supported Go releases...

[agnivade]

Reopening again.