6 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	d00dac140b	A build module takes asks only within its node's build hours ... The operator, 2026-10-26 21:18: g14 builds only from 18:00 to 06:00. A build-hours setting names a window per node in its local time (crossing midnight allowed, absent = any hour); outside it the capacity judged by is 0, running steps finish, and the puller wakes on one timer at the next edge. The change is said in the log and in capacity.<node> with the window and when it opens.	2026-10-26 21:21:37 +01:00
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	527d87613e	Without the composer's share a step has no thread limit; with it, the share over the module's own capacity (ADR 0553 round 2) ... Review round 2: change A must not slow builds before any slice exists, so a module given no share sets no GOMAXPROCS. The slice's quota bounds the total; threads only size one step, from the node's share over the module's own capacity (shanks: 24 x 50% / 3 = 4). The share is the node-engine's own config.	2026-10-26 14:39:39 +01:00
jschoubben	852ba81c5a	Build seats yield to one shared slice per node; the composer half waits for the engines (ADR 0553, issue 1806) ... Review round 1: the decoder type ships before any composer can emit it, so a routine SDK bump never sends yields to an engine that refuses them; the composer half moves to a later change. Every yielding process of a node goes into one top-level slice, meshyield.slice, so the three build modules share one quota instead of taking one each; the share is one node value, node-tools' build-cpu-share, and each step's threads divide it by every build slot of the node (words from the composer, a conservative fallback without them).	2026-10-26 14:20:05 +01:00
jschoubben	04902ff24a	Build seats yield: idle priority and a per-node processor cap on their runtimes, threads per step within it (issue 1806) ... The operator's desktop slows while it builds: the Go build runtime took 1650% of shanks' 24 processors with nothing holding it back. A build seat's holder now runs its runtime at idle priority under its node's cpu-cap share (declaration Yields, composed from Seat.Yields and the module's cpu-cap setting), and buildcpu/buildstep give each step its part of that cap in threads.	2026-10-26 13:37:00 +01:00
jschoubben	8cd22892a3	Read a node's build capacity from the build module's own setting at every pull, defaulting to the builder's values, so the control-node pulls nothing (issue 1887 A7, ADR 0525 §5)	2026-10-23 15:23:03 +02:00