Skip to content

Pin the browser integration test job to ubuntu-24.04 - #1454

Merged
aram356 merged 1 commit into
mainfrom
fix/pin-browser-test-runner
Oct 27, 2026
Merged

aram356 merged 1 commit into
mainfrom
fix/pin-browser-test-runner

Conversation

@aram356

@aram356 aram356 commented Oct 27, 2026

Copy link
Copy Markdown
Collaborator

Why

ubuntu-latest moved to 26.04, and playwright install --with-deps chromium now fails:

Error: ERROR: Playwright does not support chromium on ubuntu26.04-x64

No browser gets installed, so every Playwright test then fails in a few milliseconds. This is repo-wide and not specific to any branch: the browser integration tests check passed on runs from 2026-10-26 and fails on the first runs from 2026-10-27, with Image: ubuntu-26.04 in the job log.

Found while CI was red on #1300; the failure is unrelated to that PR's changes, so the fix is here rather than mixed into it.

What changed

Pin only the browser-tests job to ubuntu-24.04.

The other jobs are deliberately left floating:

  • integration tests, integration tests (Fastly EC lifecycle), and prepare integration artifacts do not drive a browser.
  • cargo test (axum native) does use Chrome, but obtains it through browser-actions/setup-chrome, which works on 26.04. Verified: on the same 26.04 run where the browser job failed, that job passed.

Testing

  • actionlint .github/workflows/integration-tests.yml passes.
  • Only the browser job's runs-on changes; the other three stay ubuntu-latest.
  • The real check is this PR's own browser integration tests run, which exercises the pinned image.

Unpin once the pinned Playwright version supports the newer image.

GitHub moved ubuntu-latest to 26.04, and `playwright install --with-deps
chromium` now fails with "Playwright does not support chromium on
ubuntu26.04-x64". No browser is installed, so every Playwright test fails in a
few milliseconds. Runs on 2026-10-26 passed; the first runs on 2026-10-27
failed on every branch.

Pin only this job. The other integration jobs do not drive a browser, and the
Axum job gets Chrome through browser-actions/setup-chrome, which works on the
newer image. Unpin once the pinned Playwright version supports it.
@aram356
aram356 merged commit fd2bf10 into main Oct 27, 2026
24 checks passed
@aram356
aram356 deleted the fix/pin-browser-test-runner branch October 27, 2026 05:33
prk-Jr added a commit that referenced this pull request Oct 27, 2026
Resolve the conflicts with #1222, #1290, #1413 and #1454 semantically:

- Apply #1413's request-host validation to every selected source except
  the authenticated forwarder, including ingress and adapter runtime
  origin, and keep RequestInfo::from_request fallible.
- Carry trace_bootstrap through #1290's async EOF driver so trace-active
  documents keep their bootstrap on that path.
- Move the trace auth log test onto #1222's shared WarningCapture so the
  two test loggers no longer race for the process-global slot.
- Adapt main's tests that relied on unauthenticated forwarded headers,
  and rewrite main's host-selection CHANGELOG entry to the merged order.
prk-Jr added a commit that referenced this pull request Oct 27, 2026
The ubuntu-latest image moved to 26.04, where Playwright cannot install chromium. Apply the same pin #1454 gave the browser integration tests job.
jwrosewell pushed a commit to jwrosewell/trusted-server that referenced this pull request Oct 28, 2026
GitHub moved ubuntu-latest to 26.04, and `playwright install --with-deps
chromium` now fails with "Playwright does not support chromium on
ubuntu26.04-x64". No browser is installed, so every Playwright test fails in a
few milliseconds. Runs on 2026-10-26 passed; the first runs on 2026-10-27
failed on every branch.

Pin only this job. The other integration jobs do not drive a browser, and the
Axum job gets Chrome through browser-actions/setup-chrome, which works on the
newer image. Unpin once the pinned Playwright version supports it.

(cherry picked from commit fd2bf10)
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.

2 participants