wasm-pack test --headless --chrome timing out

[notdanilo]

🐛 Bug description

wasm-pack test --headless --chrome returns an error with the following message:

     Running /home/runner/work/ide/ide/target/wasm32-unknown-unknown/debug/deps/physics_simulator-452494b2d896c9ff.wasm
Executing bindgen...                              
                                                  
Running headless tests in Chrome on `http://127.0.0.1:44987/`
Try find `webdriver.json` for configure browser's capabilities:
Not found
Starting new webdriver session...                 
Visiting http://127.0.0.1:46113...                
Loading page elements...                          
Waiting for test to finish... 
                                                  
failed to detect test as having been run
output div contained:
    Loading scripts...

                                                  
driver status: signal: 9
driver stdout:
    Starting ChromeDriver 79.0.3945.36 (3582db32b33893869b8c1339e8f4d9ed1816f143-refs/branch-heads/3945@{#614}) on port 44987
    Only local connections are allowed.
    Please protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code.

driver stderr:
    [1580797827.234][SEVERE]: Timed out receiving message from renderer: 299.961
    [1580797827.236][SEVERE]: Timed out receiving message from renderer: -0.002

                                                  
Error: some tests failed

🤔 Expected Behavior

To be able to run the tests with the loaded scripts.

👟 Steps to reproduce

It's not easily reproducible as it randomly happens.

🌍 Your environment

Include the relevant details of your environment.

wasm-pack version: 0.8.1 rustc version: 1.40.0-nightly (4f03f4a98 2019-11-12) chromedriver: 79.0.3945.36 google-chrome: 79.0.3945.*

[ashleygwilliams]

@notdanilo chromedriver/chrome just updated to a v80- could you try again and let me know if you continue to see the issue (i understand that it's hard to repro)? we've gotten some reports and seen some failure for wasm-pack test locally with folks who are on windows+rust nightly- do you happen to be on windows?

[notdanilo]

@ashleygwilliams thanks for your reply. I can't remember if I ever saw this problem happening on Windows. It probably happened. But the last time it occurred was on Ubuntu (our Linux CI works faster than Windows):

https://github.com/luna/ide/pull/154/checks?check_run_id=431691665

I will try to update Chrome to v80 and test it for a week. I will report back after this period.

[expenses]

I'm getting the same thing on a project that creates websocket connections. Maybe this is the problem?

[0x8f701]

encountered the same issue: https://github.com/GopherJ/webgpu-shaders/actions/runs/10551768939/job/29229659653

[Kofituo]

I'm getting the same thing on a project that creates websocket connections. Maybe this is the problem?

I'm facing this same issue but with Firefox. Is there any fix for it?

[crajcan]

I'm getting the same thing on a project that creates websocket connections. Maybe this is the problem?

I'm facing this same issue but with Firefox. Is there any fix for it?

I'm having this issue as well

[Kofituo]

I'm getting the same thing on a project that creates websocket connections. Maybe this is the problem?

I'm facing this same issue but with Firefox. Is there any fix for it?

I'm having this issue as well

Set the env variable WASM_BINDGEN_TEST_TIMEOUT: 10000000 For instance

WASM_BINDGEN_TEST_TIMEOUT=10000000 npm run serve