What the numbers show
build + test ≥ 5 min and ≥ 60% of the jobWhen most of a job is compiling and running tests, the job is CPU- and memory-bound. More cores only help if the build tool and test runner use them, so check parallelism flags too.
The change
Move the job to a bigger or faster runner
jobs: build:- runs-on: ubuntu-latest+ runs-on: graphideLet the tools use every core
- run: cargo build --jobs $(nproc)- run: make -j"$(nproc)"- run: npx jest --maxWorkers=100%Runner options
Verify the verdict stays the same
- 01Run the same commit on both runners.
- 02The job's conclusion matches on both.
- 03The test count and the build artifacts match.
- 04Paste both runs into /baseline and read the per-job difference.