Skip to content

fix(otter): release checks pass after the 2026-11-12 sync - #83

Merged
Laurin-Notemann merged 4 commits into
mainfrom
fix/otter-sync-2026-11-12-tests
Nov 12, 2026
Merged

Laurin-Notemann merged 4 commits into
mainfrom
fix/otter-sync-2026-11-12-tests

Conversation

@Laurin-Notemann

Copy link
Copy Markdown

The first nightly after the 2026-11-12 sync (run 43157389536) failed its test gates: vp check formatting in two files, two server tests still using T3's launchd label and data home, the settings Tab test expecting the Extensions section that web hides, and Chromium running out of memory in the web browser tests ("Browser connection was closed").

Fixed the formatting and the Otter names in the tests, and made the Tab test skip Extensions like the nav does. The adaptation script now runs each web runner's unit tests separately and splits its browser share in two, so every half gets a fresh Chromium. This is #80's fix adapted to upstream's runner matrix.

Done by Claude Opus 5.5 in Claude Code.

🤖 Generated with Claude Code

Laurin-Notemann and others added 4 commits November 12, 2026 06:05
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>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Two sessions per runner still ran Chromium out of memory on both web runners.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Laurin-Notemann
Laurin-Notemann merged commit ec02d09 into main Nov 12, 2026
21 checks passed
@Laurin-Notemann
Laurin-Notemann deleted the fix/otter-sync-2026-11-12-tests branch November 12, 2026 05:39
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