The rest go at once after the first passes, and a gate survives a new controller (hq ADR 0353) #312

Merged

mesh-admin merged 4 commits from fix/the-rest-in-parallel-and-gates-survive-a-new-controller into main 2026-10-13 23:43:02 +00:00

Conversation 4 Commits 4 Files Changed 10

+1172 -55

4 Commits

Author	SHA1	Message	Date
jschoubben	b482122d66	Say a read error of a silent rest, and keep the node-engine one at a time in a kept step (hq ADR 0353) ... An empty answer on a read error would clear release-silent unseen.	2026-10-14 01:26:00 +02:00
jschoubben	2f5cc146fe	Keep a walk's sends to what was kept, and say a silent rest (hq ADR 0353 review) ... A release's own gates held its other sends back for ever; an adopted send lost what the machine ran before; a kept send could grow a build no gate passed; a take-over matched by commit alone; a rest that went silent ended done. The node-engine and the resolver still go one machine at a time, since a fault that cuts a machine off shows only as silence.	2026-10-14 01:18:51 +02:00
jschoubben	c2ea9b4c51	Send the rest at once after the first passes, and resume a stored gate (hq ADR 0353) ... A release now sends every other machine in one step once its first machine passed, each judged by its own gate; a failing one is put back without stopping the others, a silent one is left. A send is kept before it is made, and a machine already sent what a gate is for is not sent again: the gate counts from that send and takes over another walk's readings of the same build there.	2026-10-14 01:06:49 +02:00
jschoubben	b03d257f81	Test that the rest go at once after the first passes and a gate survives a new controller (hq ADR 0353) ... The release walked four machines one after another in eleven minutes, and a new controller re-sent and re-judged a build its machine already ran.	2026-10-14 01:06:49 +02:00