.github/workflows: Wasm tests often fail with `websocket url timeout reached` - Githubissues

hajimehoshi / ebiten

Ebitengine - A dead simple 2D game engine for Go

https://ebitengine.org

Apache License 2.0

10.41k stars 635 forks source link

.github/workflows: Wasm tests often fail with `websocket url timeout reached` #2982

Open hajimehoshi opened 2 months ago

hajimehoshi commented 2 months ago

Ebitengine Version

main (10d96601250f34a9e7d0ba5691b04edb230c0d3b)

Operating System

[X] Windows
[ ] macOS
[X] Linux
[ ] FreeBSD
[ ] OpenBSD
[ ] Android
[ ] iOS
[ ] Nintendo Switch
[ ] PlayStation 5
[ ] Xbox
[X] Web Browsers

Go Version (`go version`)

Go 1.19-1.22

What steps will reproduce the problem?

Run the CI tests.

What is the expected result?

The Wasm tests pass.

What happens instead?

The Wasm tests often fail.

https://github.com/hajimehoshi/ebiten/actions/runs/8965068190

websocket url timeout reached

Anything else you feel useful to add?

No response

hajimehoshi commented 1 month ago

Now this doesn't happen?

hajimehoshi commented 1 month ago

This happens again.