Tries record their asks; the try limit counts tries on a build node; build_usage shows capacity, hours and steps (issue 1890) #78

Merged

mesh-tools merged 6 commits from fix/capacity-follows-cpu-share into main 2026-10-26 20:33:35 +00:00

Conversation 2 Commits 6 Files Changed 11

+287 -38

6 Commits

Author	SHA1	Message	Date
jschoubben	ea94f9234c	Merge remote-tracking branch 'origin/main' into fix/capacity-follows-cpu-share	2026-10-26 21:29:44 +01:00
jschoubben	c19468b04e	Pin the checker and the view at mesh-sdk 805b4d9: the capacity work merged with sdk main	2026-10-26 21:29:44 +01:00
jschoubben	c47afd8f4b	build_usage says a seat's build hours, and when it is outside them ... A build module's capacity.<node> now carries its node's build window (the operator, 2026-10-26: g14 builds only from 18:00 to 06:00); the seat shows it, outside it says it takes nothing new, and a value the module cannot read shows as any hour with the value and why. The checker's and the view's SDK pin moves to mesh-sdk d00dac1.	2026-10-26 21:22:36 +01:00
jschoubben	d6bd31a166	Say the try limits as what they are: a check when a try is asked ... Tries let in while waiting may later all run at once; each node's build capacity bounds what runs on it (review of issue 1890's try cap).	2026-10-26 20:11:08 +01:00
jschoubben	c0a4b139a2	A try queued behind the build seat's checks no longer blocks the next try ... Only tries a build node holds count toward the 4 at once; tries waiting for a node are bounded apart at 8, and the refusal names both counts (issue 1890: at 19:53 four tries queued behind 44 checks for up to 47 minutes refused every further try).	2026-10-26 20:05:51 +01:00
jschoubben	6d60953f98	A running try names its asks and where each stands; build_usage says a seat's CPU-bound capacity ... The checker wrote a try's asks only at its end, so a 31-minute try could not be told queued from running (issue 1890). The try's record now names each ask as it is put, then the node that took it, its state and the phase its step says, written on the step key's own changes. build_usage names a running try's asks and takes a build module's capacity.<node> (configured bounded by its node's build CPU, issue 1806's follow-up) when it is current with mesh-config.	2026-10-26 19:58:39 +01:00