Development record
TestAFullPageOfTheForgesRecordKeepsNoMarkForWhatItDidNotCover (internal/surface/cli/status_forge_page_test.go) fails when the machine is slow enough. It runs abcd status with the production budget for each forge lookup, and in a preflight's race stage on 2026-10-28, at a one-minute load near 180, a git rev-list ran past that budget. So the reply said the forge's record was not placed in full, where the test wants it said to be read in part. The branch under test changed only records, and the same test passed in the stage before.
issueopenminoriss-2610281338119523
TestAFullPageOfTheForgesRecordKeepsNoMarkForWhatItDidNotCover (internal/surface/cli/status_forge_page_test.go) fails when the machine is slow enough. It runs abcd status with the production budget for each forge lookup, and in a preflight's race stage on 2026-10-28, at a one-minute load near 180, a git rev-list ran past that budget. So the reply said the forge's record was not placed in full, where the test wants it said to be read in part. The branch under test changed only records, and the same test passed in the stage before.
Frontmatter
| id | iss-2610281338119523 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610281338119523-testafullpageoftheforgesrecordkeepsnomar.md
open on GitHub ↗ · commit history ↗