Development record
CI's plain unit test step, which runs on a records-only or docs-only change, sets no -timeout, so each package inherits go test's ten-minute default. The implement loop package's plain time on the ubuntu runner has grown from 466s to 593s across recent runs and crossed 600s on 2026-10-30 with no test hung, failing a records-only pull request and dropping it from the merge queue. The race steps and make preflight already declare a 40-minute budget.
issueresolvedmajoriss-2610302058222905
CI's plain unit test step, which runs on a records-only or docs-only change, sets no -timeout, so each package inherits go test's ten-minute default. The implement loop package's plain time on the ubuntu runner has grown from 466s to 593s across recent runs and crossed 600s on 2026-10-30 with no test hung, failing a records-only pull request and dropping it from the merge queue. The race steps and make preflight already declare a 40-minute budget.
Frontmatter
| id | iss-2610302058222905 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-2610302058222905-ci-s-plain-unit-test-step-which-runs-on.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610302058287983The implement loop package's plain test time on the ubuntu CI runner, run as one process, grew from 466s to 593s across recent runs and then crossed 600s; internal/surface/cli ran at 400 to 550s. The goroutine dumps show the time going to git process spawns in the state and tracked-file reads. CI's plain step now shards both packages as make preflight does and declares a 40-minute package budget (iss-2610302058222905), but the packages keep growing, and the margin narrows again at this rate.