Development record
TestThePromptThatNamesTheSessionCarriesTheStatus (internal/surface/cli/status_hook_title_test.go) requires the status line in each of its four subtests under the shipped hook budget (one second) and status read cap (600 ms), with no override, so a loaded runner can spend the read's share and leave the status unavailable, failing it the way iss-2610180735158998 failed.
issueresolvedminoriss-2610181153278714
TestThePromptThatNamesTheSessionCarriesTheStatus (internal/surface/cli/status_hook_title_test.go) requires the status line in each of its four subtests under the shipped hook budget (one second) and status read cap (600 ms), with no override, so a loaded runner can spend the read's share and leave the status unavailable, failing it the way iss-2610180735158998 failed.
Frontmatter
| id | iss-2610181153278714 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610181153278714-testthepromptthatnamesthesessioncarriest.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610180735158998TestThePromptHookShowsEachAnnouncementOnce (internal/surface/cli/status_hook_test.go) runs the prompt hook at the shipped one-second budget with the status read capped at its shipped 600 ms, and asserts the announcement is shown, so a loaded runner can spend the read's share and fail it the way iss-2610180712063858 failed. Its budget is part of what it tests (the hook returns inside its second with an origin that would hang), so stretching the budget there is a choice about what the test proves, not a tolerance fix.