the project lead, 7 October 2026 15:02 UK: build-1 at load 139 / 114 / 90 with both slots held and a 1 h 40 min queue while build-2 read 4.5 with free slots, because the class router pinned each class to its box. Now lib.sh bs_route_spill reads the preferred box (free slots, 1-minute load) with one ssh and hands the job to the other box when the preferred one has no free slot or sits above load 64 and the other qualifies; neither qualifying queues on the class's own box. The decision travels as BR_ROUTE_* into the JSONL "route" object for the dashboard. build-2's slots file reads 3; everything on box 2 runs at nice 10 / 32 cores / -j 32, and a bounded run takes the band its slot owns so three never share a core. Self-test tools/ci/route-spill-check.sh (thirteen cases) in the gate. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| build-server | ||
| cloud-devnet | ||
| cross | ||
| devnet | ||
| fast-time | ||
| gpu-bench | ||
| seed-nodes | ||