Development record
Two status-line deadline tests fail under machine load and pass in isolation: TestStatuslineSlowBranchStillRendersThePartialRow (stdout empty, the call returned in 2.003s against a 2s git budget) and TestStatuslineKillsTheRootCommitGit (the root-commit git timed out at 2s, so the 'git did not say whether abcd manages the checkout' note was replaced by 'git did not name the checkout within 2s'). Both failed in a make preflight of feat/local-model-pin-r2 on 2026-10-23 at a load of roughly 27 to 40 on 16 cores, and both pass on origin/main and on that branch when run alone. The first is the test iss-2610090642407850 resolved on 2026-10-09; its timing margin is gone again under load, and the second shows the same root cause: a real 2-second budget raced against git on a loaded machine.
Two status-line deadline tests fail under machine load and pass in isolation: TestStatuslineSlowBranchStillRendersThePartialRow (stdout empty, the call returned in 2.003s against a 2s git budget) and TestStatuslineKillsTheRootCommitGit (the root-commit git timed out at 2s, so the 'git did not say whether abcd manages the checkout' note was replaced by 'git did not name the checkout within 2s'). Both failed in a make preflight of feat/local-model-pin-r2 on 2026-10-23 at a load of roughly 27 to 40 on 16 cores, and both pass on origin/main and on that branch when run alone. The first is the test iss-2610090642407850 resolved on 2026-10-09; its timing margin is gone again under load, and the second shows the same root cause: a real 2-second budget raced against git on a loaded machine.
Frontmatter
| id | iss-2610230814127624 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610230814127624-the-status-line-deadline-tests-race-a.md
open on GitHub ↗ · commit history ↗
mentions2
- 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.
- iss-2610230826159867A resolved issue's resolved_by.commit goes stale when the commit it names is rewritten before it reaches the default branch, and nothing follows it. On 2026-10-22/23 lane C re-stamped records by hand three times: twice after rebasing a stacked branch onto a moved parent, and once after re-wording an unpushed commit to drop a scoped prefix. Each time RS003 found the stamp unreachable and the ledger gate failed until the sha was edited by hand. Two designs are open and not chosen here. A lookup by patch-id follows a reworded or rebased unpushed commit to its new sha, but does not survive a squash merge, which already rewrites the cited commit out of existence and which RS003 reports. Stamping at land time instead (resolve names the change, the land step writes the merged sha) survives a squash but needs the land step to own the stamp.