Repository navigation
CI: report lint errors before the browser tests and run browser specs on four workers - #3566
Conversation
… four workers Validate Changes spent about 56 of its 60 minutes in the browser smoke test: 889 Playwright tests on one worker, with lint and typecheck only afterwards. - Run Checks now comes first and a failed gate skips the browser run. - The browser specs run one file per worker: four workers on hosted runners, two on rootless workers; local runs keep one worker. - creation-short-window.pw.ts, 18% of the suite's test time, spreads its independent tests over the workers. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
|
CI failed: Validate Changes Please investigate and fix this CI failure.
Failure evidence
|
Checks FailedValidation failed during setup, tests, CLI packaging, linting, or build checks. View Logs |
|
CI failed: Full Test Suite Shard 2/4 Please investigate and fix this CI failure.
Failure evidence
|
|
CI failed: Full Test Suite Shard 4/4 Please investigate and fix this CI failure.
Failure evidence
|
|
CI failed: Run Full Test Suite Please investigate and fix this CI failure.
Failure evidence
|
Full Test Suite ResultsValidation failed during: Test shard (shard 2), Test shard (shard 4).
View shard 2/4 outputView shard 4/4 outputDetails truncated; see the uploaded artifacts for complete failure rows and logs. |
Full Test Suite ResultsValidation failed during: Test shard (shard 2), Test shard (shard 4).
View shard 2/4 outputView shard 4/4 outputDetails truncated; see the uploaded artifacts for complete failure rows and logs. |
|
/merge |
# Conflicts: # CHANGELOG.md
Why
Validate Changestakes about an hour on a UI-touching PR. The browser smoke test runs 889 Playwright tests on one worker (about 56 minutes), and lint runs only after it, so a lint warning is reported an hour after the push.What changes
Run Checksnow runs before the two browser steps, so a lint or typecheck error is reported within a few minutes. WhenRun Checksfails, the two browser steps are skipped and the job fails without spending the browser time; the browser tests run on the next push once checks pass.PROPR_BROWSER_TEST_WORKERSto 4 on GitHub-hosted runners and 2 on self-hosted ones, andpropr-ui/playwright.config.tsreads it (default 1, so local runs are unchanged).fullyParallelstays off: files run in parallel, tests inside a file stay in order.creation-short-window.pw.tsis the one long spec whose tests are independent, so it opts into parallel mode within the file.test/ciWorkflowDeduplication.test.mjsasserts the new step order and the worker setting.docs/ci-runners.mdandCHANGELOG.mddescribe the change.Verification
node --test test/ciWorkflowDeduplication.test.mjs: 11 of 11 pass.actionlintonpr-build-check.yml: clean.This PR's own
Validate Changesrun is the real measurement on a hosted runner.🤖 Generated with Claude Code