4 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	fc4f57c4b3	Restart an ask's bound at each run's start, also on the same node, so a step redelivered after its build module was replaced is not cut by the killed run's time (issue 1887, review: issue 734 path; ADR 0525 §6)	2026-10-23 16:36:46 +02:00
jschoubben	88fa74ce5e	Bound an ask's step from its start on the node that took it, not from its put, so an ask waiting in its stream during a large rebuild is never failed and asked twice (issue 1887, review round 2 item 1; ADR 0525 §3, §6)	2026-10-23 16:32:21 +02:00
jschoubben	6003da0a58	Put an ask on its build seat's stream and read its step, and name a building key's asks, so the builder and the checker ask no node and a restarted builder never asks twice (issue 1887 A4a, A4b)	2026-10-23 15:43:59 +02:00