fix(ci): increase karma capture timeout to avoid flaky Chrome launches#544
Merged
Conversation
ChromeHeadless intermittently failed to capture within the previous 5s timeout on cold CI runners, causing spurious JS Unit failures on master even for commits touching no JS (e.g. translation-only changes). Raise captureTimeout to 60s (Karma's default) and tolerate a couple of transient browser disconnects so a slow launch no longer fails the job. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>
phil-davis
approved these changes
Jul 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The JS Unit CI job failed on master (run 29004103213) for a translation-only commit (#534) that touches no JavaScript.
The logs show the tests never ran — ChromeHeadless failed to launch within the configured timeout:
Re-running the identical job with no code changes passed, confirming a flaky, environmental launch timeout rather than a code regression.
Root cause
js/karma.conf.jssetcaptureTimeout: 5000(unchanged since 2014). 5 seconds is too tight for a cold GitHub Actions runner to download and spawn headless Chrome — Karma's default is 60000ms.Fix
captureTimeoutfrom5000→60000(Karma default).browserDisconnectTolerance: 2to ride out transient launch hiccups.No test logic is changed. This only affects how long CI waits for the browser to come up.
🤖 Generated with Claude Code