fix(ci): pin Lighthouse's Chrome so the budget gate isn't runner-fleet noise - #1716
Conversation
…t noise lighthouse-budget measured the ambient Chrome the ubuntu-24.04 runner image ships instead of a pinned binary. On 2026-08-07 the runner fleet served HeadlessChrome/150 and /151 to jobs minutes apart, so every grading run hit the "baseline measured by a different browser" fail-closed path (working as designed — a browser bump is indistinguishable from a real regression, so the grader refuses to compare across it). Refreshing the baseline for whichever version showed up (#1690) only bought a few hours before the next mismatched runner failed it again. Install Playwright's managed Chromium (same binary/cache the Production UI and Visual baselines jobs already use, pinned by package-lock.json) and pass its executablePath via PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATH, which run-lighthouse-budget.mjs already reads into CHROME_PATH for the lighthouse CLI. No script changes needed.
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 42 minutes Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Comment |
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Codex P2 on PR #1724: the red advisory is a stale Chromium 150 baseline overwrite from #1710 against a job already pinned to Playwright Chromium 151 (#1716), not a fresh CI-runner 150→151 bump. Prefer restoring or comparing the known 151 baseline over a blind --update. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
2 participants
lighthouse-budget measured the ambient Chrome the ubuntu-24.04 runner image
ships instead of a pinned binary. On 2026-08-07 the runner fleet served
HeadlessChrome/150 and /151 to jobs minutes apart, so every grading run hit
the "baseline measured by a different browser" fail-closed path (working as
designed — a browser bump is indistinguishable from a real regression, so
the grader refuses to compare across it). Refreshing the baseline for
whichever version showed up (#1690) only bought a few hours before the next
mismatched runner failed it again.
Install Playwright's managed Chromium (same binary/cache the Production UI
and Visual baselines jobs already use, pinned by package-lock.json) and pass
its executablePath via PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATH, which
run-lighthouse-budget.mjs already reads into CHROME_PATH for the lighthouse
CLI. No script changes needed.