Development record
A go test started outside the load gate adds load that only a waiter can see. The gate names such runs by pid on its own waiting line (iss-2610241130157455) and the LOAD rules teach gating them, but nothing shows them when no waiter is there to print that line, and nothing tells a session or a sub-agent at the moment it starts one, so the one-minute load rises with no cause on record.
issueopenminoriss-2611050840333155
A go test started outside the load gate adds load that only a waiter can see. The gate names such runs by pid on its own waiting line (iss-2610241130157455) and the LOAD rules teach gating them, but nothing shows them when no waiter is there to print that line, and nothing tells a session or a sub-agent at the moment it starts one, so the one-minute load rises with no cause on record.
Frontmatter
| id | iss-2611050840333155 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2611050840333155-a-go-test-started-outside-the-load-gate.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610241130157455Plain go test runs that sessions start outside the load gate keep the one-minute load above the gate's limit, so the gated preflights starve: on 2026-10-24 three preflights of this account waited 18, 36 and 54 minutes at 'abcd implement load --wait' (load 26 to 76 against a limit of 20 on 10 cores) while three ungated 'go test -timeout 40m' runs of other sessions (internal/surface/cli, internal/core/identity and its neighbours) ran beside them, and the session filing this had itself run internal/core/implement/... and internal/surface/cli ungated earlier the same morning. The gate counts a running make preflight and a go test -race run as occupancy, but a plain go test only as load, so the runs that skip the gate are the ones that hold it shut for the runs that use it.