7 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	3f8b0b4248	Build modules take asks only within their node's build hours ... mesh-build-go, -node and -image declare build-hours (node=HH:MM-HH:MM in the node's local time, empty = any hour) and hand it to the SDK puller (the operator, 2026-10-26: g14 builds only from 18:00 to 06:00); their SDK pin moves to mesh-sdk d00dac1, which has it.	2026-10-26 21:22:09 +01:00
jschoubben	245143d948	Build modules run at most as many steps as their node's build CPU gives, and say a check's phases ... Each of mesh-build-go, -node and -image declares cores-per-step (6, 2, 2) and hands it to the SDK puller, which bounds the configured capacity by floor(slice quota cores / cores-per-step), read live; thread limits and the status tools follow the effective capacity (issue 1806's follow-up: three Go checks on shanks' 12-core slice starved past the 30-minute step bound). mesh-build-go says its lint and test phases with the ask id (issue 1890).	2026-10-26 19:55:31 +01:00
jschoubben	ac2c56f2a9	Build modules: steps end by compare-and-set; pin the sdk head with the review's fixes (issue 1890)	2026-10-26 13:44:00 +01:00
jschoubben	5fe5f26e7e	Build modules: a restart ends the steps it left running, a step shows what it is, build_*_step_end ends one (issue 1890)	2026-10-26 13:27:46 +01:00
jschoubben	78d26867d2	Give the build modules' steps state an age of two days, and keep a node's pause in a pauses state of its own ... mesh-build-go's steps bucket filled to the bus's 64 MiB cap (27,370 keys, none ever removed) and refused the end of a passed check, so the check read failed; mesh-build-node's (17.8 MB) and mesh-build-image's grow the same way. A step's key is per step: its reader reads its end within the step's bound, and a check's verdict is kept by the checker, so two days is ample. The node's pause key lived in the same bucket and would have ended by itself; it moves to a pauses state without an age (mesh-sdk fix/steps-bucket-ages, Puller.PausePut). No node is paused today, so nothing is carried over.	2026-10-25 18:53:04 +01:00
jschoubben	3138570c6b	Let the build modules follow their capacity on the bus, so a node raised from capacity 0 starts pulling (issue 1887) ... g14's Go builder sat idle at capacity 2 because nothing woke its parked puller. mesh-build-go, mesh-build-node and mesh-build-image now pin mesh-sdk b9911dc1, whose puller watches the config value capacity as mesh-config resolved it and wakes on each change, and hand it that watch.	2026-10-25 17:28:00 +01:00
jschoubben	8356d30e1b	Pull the Node build seat's asks beside the tools, delivery first and at most the node's capacity (issue 1887 A3node, ADR 0525 §2-§6)	2026-10-23 15:39:30 +02:00