Development record
CI's Linux check job runs within about two minutes of its 30-minute timeout, so a branch that adds tests can be cancelled with no test failing. On 2026-10-27 the two successful Linux check jobs before 07:00Z took 28 minutes each, their race stage over internal/ about 25 of them. Pull request #1147's job was cancelled at 30m16s while its race stage was still printing results, though every gate and the race run had passed in make preflight. A cancelled required check costs a rerun, and the merge-queue entry runs the same job under the same limit.
issueresolvedmajoriss-2610270815076960
CI's Linux check job runs within about two minutes of its 30-minute timeout, so a branch that adds tests can be cancelled with no test failing. On 2026-10-27 the two successful Linux check jobs before 07:00Z took 28 minutes each, their race stage over internal/ about 25 of them. Pull request #1147's job was cancelled at 30m16s while its race stage was still printing results, though every gate and the race run had passed in make preflight. A cancelled required check costs a rerun, and the merge-queue entry runs the same job under the same limit.
Grounds
- pursued: the 45-minute ceiling and the warning at 35 minutes give the race stage a measured margin over the leg's 28-minute run; a merge-group run of that leg cancelled at its ceiling, or one reaching the warning, would show it wrong
Frontmatter
| id | iss-2610270815076960 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-2610270815076960-ci-s-linux-check-job-runs-within-about.md
open on GitHub ↗ · commit history ↗