A no-move tier waits for no new report, so its walk asks the next tier (issue 648)

A build made from the source every machine running it runs is marked sent
and sent nothing, yet the tier's wait asked each machine for a report after
that marking. None follows, and the walk waited for ever. Each machine is
now judged by whether it answered its last send, the one whose builds made
the build no move.
This commit is contained in:
jochen
2026-10-14 02:18:53 +02:00
parent ca3f43c400
commit d9b86376d3
3 changed files with 118 additions and 1 deletions
+1
View File
@@ -69,3 +69,4 @@
./cmd/mesh-controller TestAFirstMachineThatFailsStillStopsTheWalk
./cmd/mesh-controller TestTheControlNodeIsSentLastInAStep
./cmd/mesh-controller TestARestMachineSilentPastItsBoundIsLeftAndSaid
./cmd/mesh-controller TestANoMoveTierWaitsForNoNewReport