adminandClaude Opus 5 15bdfdf07a A gate that stands in front of the suite delays the news it carries, so it runs beside it (#94) ...

The workflow ran everything in one job: check.sh, then build, then the e2e suite and the smokes.
The runner has two job slots and four cores, so the second slot lay idle for the whole run, and a
lint error was reported only after the full suite had passed in front of it - six minutes instead
of one.

Now `gate` and `suite` are two jobs without `needs:`. They start together, both have to pass.

The price is contention: while the gate runs, vitest and chromium share four cores, and the suite
measures text widths and frame counts, which a loaded machine reports differently. The gate
therefore caps vitest at two workers via GM_TEST_WORKERS, so two cores stay free for the browser
over the whole overlap. Locally the variable is unset and nothing changes.

Measured before the push: the cap costs vitest 4.4s (16.6s -> 21.0s), check.sh exits 0 with it,
build ok. Whether the split is worth it is a question for the runner - the expected net gain is
about 50s, and the acceptance is a measurement over at least two runs.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-09-16 15:21:18 +02:00

..

ci.yml

A gate that stands in front of the suite delays the news it carries, so it runs beside it (#94)

2026-09-16 15:21:18 +02:00