chrome tests failing

[databasedav]

getting this output on wasm-pack test --chrome --headless

[INFO]: Checking for the Wasm target...
    Finished dev [unoptimized + debuginfo] target(s) in 0.04s
[INFO]: Installing wasm-bindgen...
    Finished test [unoptimized + debuginfo] target(s) in 0.03s
     Running unittests (target/wasm32-unknown-unknown/debug/deps/ws_stream_wasm-9b438ce3fcbab7d6.wasm)
no tests to run!
     Running tests/events.rs (target/wasm32-unknown-unknown/debug/deps/events-a96f1010d81f3086.wasm)
Set timeout to 20 seconds...
Running headless tests in Chrome on `http://127.0.0.1:41261/`
Try find `webdriver.json` for configure browser's capabilities:
Not found
driver status: signal: 9                          
driver stdout:
    Starting ChromeDriver 96.0.4664.45 (76e4c1bb2ab4671b8beba3444e61c0f17584b2fc-refs/branch-heads/4664@{#947}) on port 41261
    Only local connections are allowed.
    Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
    ChromeDriver was started successfully.

Error: non-200 response code: 404                 
{"value":{"error":"invalid session id","message":"invalid session id","stacktrace":"#0 0x55a936c2fee3 \u003Cunknown>\n#1 0x55a9366fd49f \u003Cunknown>\n#2 0x55a9367264ab \u003Cunknown>\n#3 0x55a9367511ec \u003Cunknown>\n#4 0x55a93674ef42 \u003Cunknown>\n#5 0x55a93674e777 \u003Cunknown>\n#6 0x55a9366d4ff4 \u003Cunknown>\n#7 0x55a9366d5ea0 \u003Cunknown>\n#8 0x55a936c61baa \u003Cunknown>\n#9 0x55a936c77651 \u003Cunknown>\n#10 0x55a936c62b05 \u003Cunknown>\n#11 0x55a936c78a68 \u003Cunknown>\n#12 0x55a936c5705f \u003Cunknown>\n#13 0x55a9366d4b6a \u003Cunknown>\n#14 0x7f3d69902cb2 \u003Cunknown>\n"}}
error: test failed, to rerun pass '--test events'
Error: Running Wasm tests with wasm-bindgen-test failed
Caused by: failed to execute `cargo test`: exited with exit status: 1
  full command: "cargo" "test" "--target" "wasm32-unknown-unknown"

all tests past for firefox with wasm-pack test --firefox --headless

[databasedav]

updating chrome fixed this issue for me

[Naja Melan]

Hi, sorry for not reacting. I was on hollidays this week. Yes sometimes the whole testing infra can be a bit flaky. Glad to here it got resolved quite easily.