Skip to content

Pin CI's e2e job to Ubuntu 24.04 - #607

Closed
richshaw wants to merge 1 commit into
mainfrom
claude/sharp-carson-ryvv43-ci-ubuntu-24
Closed

richshaw wants to merge 1 commit into
mainfrom
claude/sharp-carson-ryvv43-ci-ubuntu-24

Conversation

@richshaw

Copy link
Copy Markdown
Owner

The problem

Every pull request's e2e job has failed since about 05:39 UTC on 25 October, in its install step, before a single test ran. ubuntu-latest now gives the Ubuntu 26.04 image, and Playwright 1.59.1 won't install Chromium there:

BEWARE: your OS is not officially supported by Playwright; installing dependencies for ubuntu26.04-x64 as a fallback.
Cannot install dependencies for ubuntu26.04-x64 with Playwright 1.59.1!
Error: ERROR: Playwright does not support chromium on ubuntu26.04-x64

It fails the same way three times, so the retry loop from #551 can't help. Seen on #604, #605 and #606. The last green runs, main at 4ed27a9 and #603, ran on the old image. main will go red on its next push.

The fix

  • e2e runs on ubuntu-24.04, the image every e2e run passed on until now. A comment says why, and to move back to ubuntu-latest with a Playwright release that supports 26.04.
  • lint-type-test still passes on 26.04 and is left on ubuntu-latest.
  • A Playwright upgrade would be the other way out, but it's a bigger change, and it's better done on its own.

Before merging

This touches .github/workflows/, so it waits for you. Its own e2e run on this PR is the test: it should get past "Install Playwright Chromium" and run the suite.


Generated by Claude Code

ubuntu-latest now gives the Ubuntu 26.04 image, and Playwright 1.59.1
refuses to install Chromium there ("Playwright does not support chromium
on ubuntu26.04-x64"), so every pull request's e2e job has failed in its
install step since, before a single test ran. The retry loop can't help.
24.04 is the image every e2e run passed on until now. The lint-type-test
job still passes on 26.04 and is left as it is.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LrYa57fvbqWjZj89iH975K

Copy link
Copy Markdown
Owner Author

Tophat: passed

This only changes CI config (.github/workflows/ci.yml), so there's nothing to click in the app. The check is the PR's own CI run on 16521f5.

Check Result What I saw
e2e on 16521f5 ✅ Ran on ubuntu-24.04. "Install Playwright Chromium" passed on the first try, and the chromium suite ran green (job 121091320057).
Before: e2e on #604's ec902eb (ubuntu-latest, now 26.04) ✅ reproduced Failed three times at install: "Playwright does not support chromium on ubuntu26.04-x64", before any test ran.
lint-type-test ✅ Still on ubuntu-latest, and green.
Copies of this commit in #604, #605, #606 and #608 ✅ Their e2e jobs went green with it. The copy in #604 (0331eb5) has the same patch-id and resulting ci.yml.

Not UX.


Generated by Claude Code

@richshaw richshaw left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review: passed (round 1)

A four-line CI change. The e2e job runs on ubuntu-24.04 instead of ubuntu-latest, which has moved to Ubuntu 26.04, where Playwright 1.59.1 refuses to install Chromium. A comment says why, and when to move back. lint-type-test stays on ubuntu-latest, since it passes there. The install retry loop from #551 is untouched, and so is every test step. Nothing is skipped or loosened.

Blocking (0)

Optional (1): a Playwright upgrade that supports 26.04 would let the pin go. That's a separate change, as the description says.

Earlier threads: none.

Checks: CI on 16521f5 is green: lint-type-test, e2e (Chromium installed on ubuntu-24.04, and the suite ran), CodeQL and Analyze. Two independent reviews of #604 and #605 confirmed that the copy of this commit carried in #604 (0331eb5) is identical: same message, same patch-id, same resulting ci.yml. So this and #604 can merge in either order without a conflict.

This waits for you because it touches .github/workflows/, which is high-risk. Until something like it is on main, every PR's e2e fails at install, so it unblocks the board.

https://claude.ai/code/session_01LrYa57fvbqWjZj89iH975K


Generated by Claude Code

@richshaw richshaw added pipeline:owner Passed; waits for the owner (UX or high-risk) and removed pipeline:working A session is working on it right now labels Oct 25, 2026 — with Claude
richshaw pushed a commit that referenced this pull request Oct 25, 2026
Playwright 1.59 can't install Chromium on the ubuntu-latest 26.04 image.
Same change as #607; a no-op once that lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GzHBSajHsqVk57cvHdphNN
richshaw pushed a commit that referenced this pull request Oct 25, 2026
ubuntu-latest is now 26.04, where Playwright 1.59 cannot install Chromium,
so e2e fails before any test runs. Same change as #607; it no-ops once
that lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HfQvAkAuqbvPj5963Aacgi
richshaw added a commit that referenced this pull request Oct 25, 2026
Nothing outside its own unit test called it; the MCP step-up 403 comes from requireBearerAuth via resolveBearerActor. flow.db.test.ts now pins that challenge's error and resource_metadata too. Also pins CI's e2e job to ubuntu-24.04 (same change as #607).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HfQvAkAuqbvPj5963Aacgi

Copy link
Copy Markdown
Owner Author

Closing: this change is already on main. #614 carried the same pin (e2e on ubuntu-24.04), so this branch's diff against main is now empty.


Generated by Claude Code

@richshaw richshaw removed the pipeline:owner Passed; waits for the owner (UX or high-risk) label Oct 25, 2026 — with Claude
@richshaw richshaw closed this Oct 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants