Use preinstalled Chrome for E2E tests - #2488
Open
ejsmith wants to merge 5 commits into
Open
Conversation
ejsmith
marked this pull request as ready for review
August 18, 2026 04:45
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
E2E_BROWSER_CHANNELis setWhy
The release run that motivated this experiment spent 6m06s installing Playwright Chromium. About 5m45s was a slow Ubuntu package download; the browser archives themselves took only seconds. Recent runs normally spend about 20-30 seconds here, but the network-dependent step has an unbounded tail.
This PR intentionally changes only the browser provisioning path so its hosted timing is attributable.
Verification
npm run checkCI=true E2E_BROWSER_CHANNEL=chrome npx playwright test --list --project=chromium(28 tests discovered)npx prettier --check playwright.config.tsMeasurement
Compare the
test-e2ejob and browser-install portion with:All three samples passed the same 28 tests. The single retry in each was the existing
list-query-cache.e2e.tsflake, not a browser-specific failure. During the paired second sample, the unchanged Chromium install took 3m56s while this FFmpeg step remained at 2s.The typical E2E job improvement is modest because the historical browser-install median was only 23 seconds, but the experiment removes a reproduced multi-minute tail: 6m06s in the motivating run and 3m56s in the paired repeat.
Breaking changes
None.