Skip to content

Run the browser suite on one worker #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
randroid88 merged 1 commit into from
Aug 3, 2026
Merged

Run the browser suite on one worker #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions apps/console-lab/playwright.config.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,16 @@ export default defineConfig({
outputDir: "../../test-results/console-lab",
fullyParallel: false,
retries: 0,
// One worker, deliberately. `fullyParallel: false` only serializes tests
// within a file; Playwright still runs files concurrently, and the worker
// count then varies with the host's core count. This suite measures real
// layout geometry and drives timing-sensitive launcher transitions, so
// concurrent load makes it flaky in a way that depends on the machine: a
// three-worker Linux run and a two-worker CI run each failed a different
// test that passed on a repeat of the identical commit. With `retries: 0`
// any such flake fails the whole run, so determinism is worth the wall
// clock. Raise this only alongside evidence that the suite is race-free.
workers: 1,
reporter: "line",
use: {
baseURL: "http://127.0.0.1:4173",
Expand Down
Loading