Skip to content

CI: Playwright jobs fail on ubuntu-latest after the runner moved to Ubuntu 26.04 (no Chromium build); pin the runner and fail the install step #1935

Closed

Description

@amrmelsayed

Problem

The scheduled Dashboard E2E workflow on main failed on 2026-11-19 (run 44485513618, head d805df2d5) with every browser launch reporting a missing Chromium executable. The same workflow passed on the same code family the day before (run 44264876229). No code change is involved.

Root cause

GitHub's ubuntu-latest label rolled from ubuntu-24.04 (image 20261111.370.1) to ubuntu-26.04 (image 20261111.196.1) between the two runs. The repo pins Playwright 1.59.1 (^1.58.0 in packages/codev, packages/artifact-canvas, apps/web), and pnpm exec playwright install chromium fails on the new image with:

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

The install step's failure does not stop the job, so the test steps run and fail at browserType.launch with "Executable doesn't exist at /home/runner/.cache/ms-playwright/chromium_headless_shell-1217/…".

Scope

Every job that runs playwright install chromium on ubuntu-latest is exposed as the rollout reaches it: .github/workflows/dashboard-e2e.yml (failing now) and the two Playwright jobs in .github/workflows/test.yml (Artifact-Canvas Browser Tests and Web Terminal Browser Tests, lines around 125 to 210), which gate every PR. Those still passed on 2026-11-18, so the rollout is gradual.

Fix shape (hypothesis for the builder to validate)

Pin the Playwright-running jobs to ubuntu-24.04 instead of ubuntu-latest, with a comment naming why, so the runner image follows an explicit decision rather than the floating label. Alternative: move Playwright to a release that ships a Chromium build for Ubuntu 26.04, if one exists at fix time; verify with playwright install chromium on a 26.04 runner before choosing it. Also make the install step fail the job (set -e behavior or a check) so a missing browser is reported at the install step rather than as dozens of launch errors.

Acceptance

  • Dashboard E2E scheduled run green on main.
  • The two Playwright jobs in test.yml green on a PR run after the change.
  • A failed browser install fails its own step.

Activity

  1. amrmelsayed commented on Nov 20, 2026

    @amrmelsayed
    CollaboratorAuthor

    On it! Working on a fix now.

  2. added 6 commits that reference this issue on Nov 20, 2026
  3. amrmelsayed commented on Nov 20, 2026

    @amrmelsayed
    CollaboratorAuthor

    Shipped in PR #1936 (merged to main at d8cacf1). The three Playwright-running jobs are pinned to Ubuntu 24.04 with a note on when to move the pin, the Decisions tab step no longer runs when the browser install failed, and a regression test keeps every Playwright job pinned and gated. Adjacent: the protocol drift-audit test now overrides the scoped registry key in-process, so a user npm config with a scoped registry no longer breaks it. Follow-up candidate held by the architect: bump Playwright to a release with an Ubuntu 26.04 Chromium build and remove the pin before Ubuntu 24.04 retires.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/releaseArea: Release tooling, version bumps, release protocol

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions