Flaky CI Failure: test-wasm WASM integration tests — Firefox browser session connection timeout
Workflow: Test
Failed run: https://github.com/xmtp/libxmtp/actions/runs/32887926385
Commit: 9655c9e
Failed jobs: test-wasm / Test (WASM)
Summary
The WASM integration test job failed during the "Run WASM integration tests" step. Vitest reported an unhandled error: it could not connect to the Firefox browser session within the timeout. All 88 tests passed (run in Chromium), and 7 of 7 test files passed, but the Firefox browser session failure caused the overall run to exit with code 1. The just wasm test-integration recipe runs yarn vitest run against both Chromium and Firefox; Firefox failed to start.
Error Details
Unhandled Errors
Vitest caught 1 unhandled error during the test run.
This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.
Unhandled Error
Error: Failed to connect to the browser session "d99939c8-178a-48fc-91d5-45f8a8f49e7d" [firefox] within the timeout.
Timeout._onTimeout node_modules/vitest/dist/chunks/cli-api.BK8pd4xc.js:465:33
listOnTimeout node:internal/timers:605:17
processTimers node:internal/timers:541:7
Test Files 7 passed (14)
Tests 88 passed (88)
Errors 1 error
Start at 19:17:12
Duration 60.04s (transform 0ms, setup 0ms, import 2.31s, tests 17.26s, environment 0ms)
error: recipe `test-integration` failed with exit code 1
##[error]Process completed with exit code 1.
Analysis
The (14) in "7 passed (14)" indicates 14 total browser-file combinations (7 test files × 2 browsers: Chromium + Firefox). Chromium ran all 7 files successfully (88 tests), but Firefox failed to establish a browser session before the timeout. This is a Vitest browser-mode infrastructure issue where Firefox did not launch or respond in time on the Blacksmith CI runner. The actual test logic is correct — no assertions failed. The affected recipe is just wasm test-integration in bindings/wasm/wasm.just:66.
This could be a transient Firefox startup failure on the CI runner, or a recurring issue with Firefox availability in the Vitest WASM test environment.
Reported by Flaky Failure Watcher
Flaky CI Failure: test-wasm WASM integration tests — Firefox browser session connection timeout
Workflow: Test
Failed run: https://github.com/xmtp/libxmtp/actions/runs/32887926385
Commit: 9655c9e
Failed jobs: test-wasm / Test (WASM)
Summary
The WASM integration test job failed during the "Run WASM integration tests" step. Vitest reported an unhandled error: it could not connect to the Firefox browser session within the timeout. All 88 tests passed (run in Chromium), and 7 of 7 test files passed, but the Firefox browser session failure caused the overall run to exit with code 1. The
just wasm test-integrationrecipe runsyarn vitest runagainst both Chromium and Firefox; Firefox failed to start.Error Details
Analysis
The
(14)in "7 passed (14)" indicates 14 total browser-file combinations (7 test files × 2 browsers: Chromium + Firefox). Chromium ran all 7 files successfully (88 tests), but Firefox failed to establish a browser session before the timeout. This is a Vitest browser-mode infrastructure issue where Firefox did not launch or respond in time on the Blacksmith CI runner. The actual test logic is correct — no assertions failed. The affected recipe isjust wasm test-integrationinbindings/wasm/wasm.just:66.This could be a transient Firefox startup failure on the CI runner, or a recurring issue with Firefox availability in the Vitest WASM test environment.
Reported by Flaky Failure Watcher