[ci] Share a single browser instance across all test suites in a single job#95589
Merged
Conversation
Contributor
Stats from current PR🔴 1 regression
📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles
Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📝 Changed Files (6 files)Files with changes:
View diffspages-api.runtime.dev.jsDiff too large to display pages-api.ru..time.prod.jsDiff too large to display pages.runtime.dev.jsDiff too large to display pages.runtime.prod.jsDiff too large to display pages-api-tu..ntime.dev.jsDiff too large to display pages-turbo...ntime.dev.jsDiff too large to display 📎 Tarball URLCommit: fdc78d7 |
Contributor
Tests PassedCommit: fdc78d7 |
bgw
added a commit
that referenced
this pull request
Jul 8, 2026
bgw
force-pushed
the
bgw/shared-browser-process
branch
from
July 8, 2026 23:02
5ef0625 to
e04c8b4
Compare
bgw
marked this pull request as ready for review
July 10, 2026 02:31
lukesandberg
approved these changes
Jul 10, 2026
| console.log(`exiting with code ${code}`) | ||
|
|
||
| if (sharedBrowserServer) { | ||
| await sharedBrowserServer.close().catch(() => {}) |
bgw
force-pushed
the
bgw/shared-browser-process
branch
from
July 21, 2026 01:15
e04c8b4 to
fdc78d7
Compare
bgw
enabled auto-merge (squash)
July 21, 2026 01:15
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
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.
The idea here is that we waste a bunch of CPU setting up each test suite by spawning an entirely new Chrome process, but playwright can share the same browser across many tests. Tests are still isolated at the browser level, just not at the OS process level.
Hoping to see some performance improvement in e2e tests. Compare to: #95617
Somewhat unscientific (single sample) results: