Development record
The load gate leaves the machine idle: a make preflight queued at its race gate still counts as Busy at the first gate, so with load.preflights=2 one preflight running its race stage and a second waiting idle at the race gate fill both slots and every other preflight waits. Observed 2026-10-28 20:02-20:15Z: four preflights queued, one test stage running, load 13 on 16 cores. MaxPreflightSlots also caps the setting at 2.
issueresolvedmajoriss-2610282016250805
The load gate leaves the machine idle: a make preflight queued at its race gate still counts as Busy at the first gate, so with load.preflights=2 one preflight running its race stage and a second waiting idle at the race gate fill both slots and every other preflight waits. Observed 2026-10-28 20:02-20:15Z: four preflights queued, one test stage running, load 13 on 16 cores. MaxPreflightSlots also caps the setting at 2.
Grounds
- pursued: with the slots set above one, a third preflight's first gate opens while one preflight sits at its race gate and another runs its race stage, and race runs stay one at a time; two race runs live at once, or a stage admitted past the load limit, would show it wrong.
Frontmatter
| id | iss-2610282016250805 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-2610282016250805-the-load-gate-leaves-the-machine-idle-a.md
open on GitHub ↗ · commit history ↗
mentions2
- dcn-26102820400854032026-10-28 — The product thinker asked on 2026-10-28 for the machine's capacity to be used, so load.preflights now takes a whole number from 1 to 4 (MaxPreflightSlots rises from the 2 of the trial in dcn-2610161814279204), and above one slot a preflight queued at its race gate takes no first-gate slot until its race run starts (iss-2610282016250805). The grounds: one race run at a time, kept by the race gate, and the load wait limit stay the bounds; each stage's go test -p is still the cores divided among the slots, never below a quarter of them; and the count is the person's own machine setting, never a repository's, one by default.
- iss-2610290033556553The load.preflights setting is described as how many preflights may be in their test stages at once, in its refusal, the help, the command page, the bundled LOAD rule and the code comments, but since iss-2610282016250805 a preflight queued at its race gate takes no slot, so a race stage can run beside as many unit stages as the setting: it bounds what the first gate admits, not what runs. The configuration chapter of the brief still says the setting takes 1 or 2, where 4 is now the most.