Skip to content

Run each browser test project in its own job - #575

Merged
CodeByZach merged 1 commit into
masterfrom
ci-projects
Nov 10, 2026
Merged

CodeByZach merged 1 commit into
masterfrom
ci-projects

Conversation

@CodeByZach

Copy link
Copy Markdown
Owner

Runs each browser test project in its own job, so Chromium's two projects (pace.js and pace.min.js) no longer run one after the other in a single job that the whole run waits for.

  • Four jobs in parallel: browser-tests (chromium pace.js), (chromium pace.min.js), (firefox pace.min.js) and (webkit pace.min.js). Tests within a job still run one at a time.
  • The final browser-tests job keeps its name, so the required checks don't change.

This PR's own checks run the new workflow.

The Chromium job ran two projects, pace.js and pace.min.js, one after the
other, so it took about twice as long as the Firefox and WebKit jobs, and
the whole run waited for it. Each project now runs in its own job, in
parallel, still one test at a time within a job. The final browser-tests
job, the required check, now passes only if every project passed.
@CodeByZach
CodeByZach merged commit eb7d40c into master Nov 10, 2026
6 checks passed
@CodeByZach
CodeByZach deleted the ci-projects branch November 10, 2026 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant