Skip to content

ci(otter): web browser tests run in four shards - #81

Closed
Laurin-Notemann wants to merge 1 commit into
mainfrom
fix/web-browser-four-shards
Closed

Laurin-Notemann wants to merge 1 commit into
mainfrom
fix/web-browser-four-shards

Conversation

@Laurin-Notemann

Copy link
Copy Markdown

#80 split the web browser tests into two processes. Shard 1 passes, but shard 2 still loses its Chromium page near the end (around file 84 to 88 of 97) on GitHub's 16 GB runners, failing Release web tests three times. Every test that ran passed.

The adaptation script now runs the browser tests in four sequential shards, so each Chromium session is shorter. The generated workflow lines are updated to match.

🤖 Generated with Claude Code

The second of two browser shards still runs Chromium out of memory near its
end on the GitHub-hosted runners, failing the nightly three times.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Laurin-Notemann

Copy link
Copy Markdown
Author

Four shards didn't help: the first browser shard lost its Chromium page at file 43 of 49, so session length isn't the cause. Closing; the intermittent page close needs root-causing instead.

@Laurin-Notemann
Laurin-Notemann deleted the fix/web-browser-four-shards branch November 11, 2026 06:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant