3 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	02f50bd9d6	A build seat's capacity follows its node's build CPU, and a running ask says its phases ... Since the build CPU cap (issue 1806) shanks' mesh-build-go kept capacity 3 inside a 12-core slice: three full checks got about 4 cores each and ran past the 30-minute step bound (issue 1890). The puller now judges by min(configured, floor(slice quota cores / cores-per-step)), the quota read live from its cgroup, says it on change and writes capacity.<node> to the pauses state. A run's phases (fetch and merge, digest, tests) are logged with the ask id and written to its running step key; Asker.Wait hands every step value to a WithStepSeen hook.	2026-10-26 19:52:54 +01:00
jschoubben	ddafe1b1aa	Build steps: a step records what it is, a restart ends the steps it left running, a tool ends one (issue 1890)	2026-10-26 13:25:13 +01:00
mesh-tools	512472c02a	Pack a build's output like the build agent and keep the steps state's shape (issues 1471, 1479), part 7 of 7	2026-10-20 20:06:48 +00:00