Development record
TestStatuslineSlowPreviousCommandIsStopped asserts the status line returns within 300ms; on the CI macOS runner it returned in 326ms for a change that did not touch it (PR #857, run 37707291322), so a fixed wall-clock budget under a race-instrumented shared runner makes it flaky.
issueresolvedminoriss-2610080243367006
TestStatuslineSlowPreviousCommandIsStopped asserts the status line returns within 300ms; on the CI macOS runner it returned in 326ms for a change that did not touch it (PR #857, run 37707291322), so a fixed wall-clock budget under a race-instrumented shared runner makes it flaky.
Grounds
- pursued: expected that TestStatusline* pass repeatedly with and without -race, including when git answers 400ms late, and that the tests still fail when a production bound is removed (group kill, previous-command timeout or git timeout, each mutated on a scratch copy). A CI or loaded-machine failure of any statusline deadline test on timing alone would show it wrong.
Frontmatter
| id | iss-2610080243367006 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610080243367006-teststatuslineslowpreviouscommandisstopp.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610090642407850TestStatuslineSlowBranchStillRendersThePartialRow failed once at 0.34s in a local landing preflight under a load average above 50; a retry passed. It is the sibling of TestStatuslineSlowPreviousCommandIsStopped, whose wall-clock budget was fixed in iss-2610080243367006, but that fix did not reach this test, so the same family can still fail under a loaded host.