Repository navigation
CI: the macOS leaks shard runs 17 to 21 minutes of its 25-minute limit; a slow runner timed out #836
Description
The macOS leaks tier's first shard (job macos, shard 0/2) runs close to its 25-minute timeout-minutes.
Recent runs:
| run | macos | macos-2 |
|---|---|---|
| main 42b0856 | 12 min | |
| main d2edbdc | 17 min | |
| #831 c521cef | 17 min | 14 min |
| #831 7f431e9 | 21 min | |
| #832 447ac64, first run | timed out at 25 (27 min with set-up) | 15 min |
| #832 447ac64, rerun | 20.5 min |
The rerun of the same commit passed in 20.5 minutes, so the timeout was runner speed, not a hang. But the margin is small, and a timed-out job keeps no log: GitHub returns BlobNotFound for it. A timeout says nothing about which suite was slow. Its missing trail then fails determinism too.
Wanted:
- Balance the two shards, or add a third. Shard 0 carries the first-shard steps (the checks, the type-check, the validation reruns, the benchmarks) as well as half the suites.
- Have ci.sh print each suite's time, as the Linux legs' timestamps let one work out, but macOS reports suites in batches.
Activity
ci: the macOS legs have 40 minutes, room for a full rebuild (#836)