Development record
TestNothingIsMarkedPastTheHooksDeadline (internal/core/claim) fails under -race on a loaded machine. It gives the whole status read a real 400ms deadline, but it tests only that a block marked after the hook's deadline keeps nothing. The read itself (git through the status state, then render) outran 400ms in the joint preflight's race stage on 2026-10-25, so PromptNotes returned 'status unavailable' and the test failed before it reached the marking. It is the same class as iss-2610241911001655: a load-dependent budget standing in front of the behaviour under test.
TestNothingIsMarkedPastTheHooksDeadline (internal/core/claim) fails under -race on a loaded machine. It gives the whole status read a real 400ms deadline, but it tests only that a block marked after the hook's deadline keeps nothing. The read itself (git through the status state, then render) outran 400ms in the joint preflight's race stage on 2026-10-25, so PromptNotes returned 'status unavailable' and the test failed before it reached the marking. It is the same class as iss-2610241911001655: a load-dependent budget standing in front of the behaviour under test.
Grounds
- pursued: the test passes at any load while marking past the deadline keeps nothing; shown wrong if it fails on a loaded machine, or passes with MarkShown keeping a block past its deadline
Frontmatter
| id | iss-2610251853204621 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610251853204621-testnothingismarkedpastthehooksdeadline.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610241911001655Two tests fail under machine load rather than on a defect: TestReadOwedHonoursDeadline in internal/core/autonomy found the read marked complete when the forge timed out, and TestHookSessionEndRetriesATransientRootFailure in internal/surface/cli ran out of retry time and staged nothing, both during a gated preflight at load 17 on ten cores