ci(coverage): run the coverage job on a sixteen vCPU runner

Merged
TH
16h ago
+2-1

Summary

The Coverage job ran on blacksmith-8vcpu-ubuntu-2404. Its suite is CPU-bound — instrumented execution plus transform — and Vitest takes its worker count from the machine, so seven workers left the rest of the run queueing. Moving the job to blacksmith-16vcpu-ubuntu-2404 doubles the workers.

One runs-on line in .github/workflows/ci.yml, plus a comment. No gate, threshold or verdict changes: the same unit-ci, coverage-model, coverage-crap-model and tmpdir-leaks gates run in the same order, with the changed-line and CRAP steps still reusing the one lcov.

Depends on #4662, which has to merge first. Three host-kit files let the runner answer for a fixture pid through /proc/<pid>/stat; those pids were unused on an 8 vCPU runner and used on a 16 vCPU one, so the job would go red at exactly this head.

Validation

Measured in CI at identical gates, Run coverage step and whole job from the Actions API.

RunnerRun coverageJobJob min x rateCost/PR
8 vCPU — 35 green runs298 s p50, 214–389338 s p505.63 x $0.016$0.090
16 vCPU — 4 runs at this head146, 146, 174, 176 s172, 179, 203, 209 s3.1 avg x $0.032$0.099
32 vCPU — run 4417625078098 s111 s1.85 x $0.064$0.118

16 vCPU samples: run 44175823688 job 1, then attempts 1–3 of 44186117469. The spread is 146–176 s against 214–389 s on 8 vCPU, so the worst 16 vCPU sample still beats the 8 vCPU p90. Every gate step was green in all four. 16 vCPU halves the wall time for about 10% more money; 32 vCPU was green only in the probe lane and costs 31% more, so 16 is the pick.

Head 02cc3803c4. node --experimental-strip-types scripts/gate/check.ts — manifest ok. Unresolved risk: the coordinate.contract.test.ts 5 s timeout seen once on #4660 was not reproduced in these four runs, on 8 or 16 vCPU.