build_usage: how much each build node is used and whether it may build, in one call #74

Merged

mesh-tools merged 4 commits from feat/build-usage-tool into main 2026-10-26 14:09:33 +00:00

Conversation 1 Commits 4 Files Changed 15

+981 -25

4 Commits

Author	SHA1	Message	Date
jschoubben	4f722899df	View: build_usage does not answer eligibility it cannot read; a resolved capacity key with no readable value is the puller's 0 ... A capacity this tool cannot read is unknown to it, not 0: the seat says eligible_known false and the node not known. A key mesh-config holds without a readable value is what the puller reads as 0, and was dropped silently.	2026-10-26 14:58:47 +01:00
jschoubben	166a918b43	View: build_usage counts keys a build module ended for being left running apart, lists every node a capacity names, and says capacity unknown when mesh-config cannot be read ... Since mesh-sdk #90 a build module ends a left-running key as failed at the moment it notices; counted as finished, such a step put hours into the medians and the time at capacity. The view takes mesh-sdk's step bound and restart reason from the SDK it now pins.	2026-10-26 14:58:47 +01:00
jschoubben	1b4c860f63	Checker: its announcement test expects tries readable, as the delivery view now reads them	2026-10-26 14:58:47 +01:00
jschoubben	3b6945b2db	View: build_usage answers how the build nodes are used in one call; the checker's tries name their asks ... The operator's question (how much are the build nodes used, is ace eligible) took six calls over four tools. build_usage reads it from the bus's states: seats held (have), capacity (mesh-config resolved), pauses, the build modules' steps by kind with left-running keys, the last hour and day with total and median time and time at capacity, the running tries, and the backlog the view program reads from the seats' streams. A try now names the asks it put, and the checker announces its tries readable, so the view tells a try's asks from a check's.	2026-10-26 14:58:41 +01:00