Repository navigation
fix(ci): keep Coroot browser checks on supported Ubuntu - #5559
Conversation
Pin the native browser job to Ubuntu 24.04 after the moving runner alias selected an OS unsupported by the pinned Playwright release. The actual merge-group job failed before browser execution. Part of #5557.
The failure is reproduced by native merge-group run 40827115612 (browser job 123292576321), before any browser scenario executes. The moving runner label selected Ubuntu 26.04, which the pinned Playwright 1.56.1 does not support. Its tagged platform selector recognizes Ubuntu 24.04; GitHub also documents pinning that image during the ongoing runner migration. Signed head The existing native browser run 40829342660 and CI run 40829342470 must settle at this exact head before an ordered independent review is requested. This remains a draft; there is no hosted success, merge or queue-recovery claim yet. |
Blocker: none Cleared 2026-10-29: Prerequisite PR 5565 merged at 2d60bc4; current main still uses ubuntu-latest in the browser job, so this runner fix remains required. Integrate current main and collect new-head CI and native browser proof. Previous record (historical): |
Cleared the merged prerequisite and integrated actual main The new native browser run 40856796709 passed. Existing CI 40856796603 and the associated Go/quality runs are still in progress. This remains draft pending settled current-head CI, an ordered substantive review and the final readiness gates. |
@coderabbitai full review |
|
|
No actionable comments were generated in the recent review.
|
cr:no-gate@f93e922. The authenticated current-PR reply, updated 2026-10-29T10:36:42Z, says the included review is rate limited for another 49 minutes (about 11:25 UTC). A fresh no-gate guard found no substantive CodeRabbit review at this head. Continue to Codex under the ordered review contract; no paid review is enabled and no source change is needed. |
@codex review |
|
Codex Review: Didn't find any major issues. Chef's kiss. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
The latest native merge-group run 40869263703 reproduced the Ubuntu 26.04 Chromium installation failure before any browser scenario ran. After the prior activity window expired and a fresh holder check found nobody working on this PR, I integrated actual main I inspected the prior-head native run 40856796709, its successful Chromium and real-browser steps, and all three preserved dashboard screenshots. The 12/8/13-panel synthetic dashboards render; absent one-day fixture history is explicit. This proves that earlier integration path, not production health or the new head. New-head CI 40872773049 and native browser validation 40872772974 are pending. This stays draft until current-head validation and independent review are complete. No queue admission, merge or post-merge recovery is claimed. |
@coderabbitai full review |
✅ Action performed
|
Current-head validation and evaluation are complete at The native browser run 40872772974 is successful at this exact head. Its browser job installed the pinned Chromium, exercised the released binary and persisted dashboards, passed the existing browser scenarios, and preserved artifact CI 40872773049 also passed at this head. The CodeRabbit recent-review summary names this head and reports no actionable comments; its author/freshness binding and the summary-verdict helper both pass. The complete conversation, review and thread read has no unresolved finding. The net diff still changes only the browser job's runner and explanatory comment; scenarios, tool/image pins, permissions, timeout and artifact requirements remain intact. The runner repair is ready for protected queue validation. This synthetic browser acceptance proves the repaired check can run; production health and downstream adoption remain separate verification obligations. |
Why
GitHub's runner upgrade prevents the required Coroot browser checks from starting and has evicted validated work from the delivery queue.
What
Run the browser check on the supported Ubuntu version so its existing scenarios can complete and delivery can resume.
Fixes #5557