Repository navigation
ci(otter): web browser tests restart Chromium between shards - #80
Merged
Merged
Conversation
One browser session over all web browser tests runs Chromium out of memory on the 16 GB GitHub-hosted runners after the 2026-11-11 sync, so the page closes partway through and Test Web and the nightly fail. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 11, 2026
Laurin-Notemann
added a commit
that referenced
this pull request
Nov 12, 2026
* fix(otter): release checks pass after the 2026-11-12 sync The first nightly after the sync failed its test gates: two files were not formatted, two server tests still used T3's launchd label and data home, the settings Tab test expected the Extensions section that web hides, and the web browser tests again ran Chromium out of memory on GitHub-hosted runners. Each web runner now runs unit tests on their own and splits its browser share in two, as #80 did before upstream sharded the job. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(otter): new git refresh test skips Otter's RPCs Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(web): command palette waits for its root list before ArrowDown Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * ci(otter): web runners split browser tests into four Chromium sessions Two sessions per runner still ran Chromium out of memory on both web runners. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
After the 2026-11-11 sync,
Test Weband the nightly'sRelease web testsfail on GitHub's 16 GB runners. Chromium's page closes partway through the browser suite, at a different file each run, after 420 to 480 of 549 files. Every test that ran passed. Upstream's 8-vCPU runners pass the same commit.The adaptation script now runs the web unit tests and the browser tests as separate processes, with the browser tests in two shards, so each shard gets a fresh Chromium. The generated workflow lines are updated to match.
🤖 Generated with Claude Code