Development record
The quiet-holder notice of iss-2610241419324875 still leaves waiters unable to tell how a load-gate holder is doing in the case that prompted it. A slow holder whose tree keeps starting short git children counts as working and is never reported, which was the 45-minute run of 2026-10-24; silence is no positive sign that a holder is working, since a waiter that joined in the last ten minutes has not measured it yet; only a same-account hold record is watched, so a holder seen only in the process table (another account's waiter running its command) is never named; and each waiter needs ten minutes of its own samples before it can say anything.
The quiet-holder notice of iss-2610241419324875 still leaves waiters unable to tell how a load-gate holder is doing in the case that prompted it. A slow holder whose tree keeps starting short git children counts as working and is never reported, which was the 45-minute run of 2026-10-24; silence is no positive sign that a holder is working, since a waiter that joined in the last ten minutes has not measured it yet; only a same-account hold record is watched, so a holder seen only in the process table (another account's waiter running its command) is never named; and each waiter needs ten minutes of its own samples before it can say anything.
Frontmatter
| id | iss-2610241457170255 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-2610241457170255-the-quiet-holder-notice-of.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610241419324875A test run admitted through the load gate keeps the shared test slot for as long as its command runs. On 2026-10-24 an agent's go test -timeout 60m of the loop suite, started at 13:19 UTC, held the slot through load-wait.json for 45 minutes while about nine preflights from every session queued behind it. It was a long, slow run, not a hung one: its goroutine dump showed it still working through tests at 30 to 70 seconds each under load, mostly in git subprocesses, so its test binary showed little CPU. The waiters could not tell whether it was working; a peer session noticed and asked its owner, who stopped it. Nothing in the gate tells the waiters how the holder is doing, nor tells the holder's owner that others are waiting.