A pending merge check says where it is: in the build queue since when, then building on which machine (hq issue 446) #202

Merged

mesh-admin merged 2 commits from fix/446-a-pending-check-says-where-it-is into main 2026-10-11 01:27:07 +00:00

Conversation 3 Commits 2 Files Changed 6

+364 -8

2 Commits

Author	SHA1	Message	Date
jschoubben	1cf56688c1	Make the gitea module the one writer of mesh/merge-gate, so a verdict always lands last (hq issue 446) ... mesh-delivery read the gate as pending and then wrote "building on", and the gitea module could write the verdict in between: the forge keeps the newest status, so a pass read pending and a failure hid under "building". The gitea module now hears the build seat's started itself and puts every write of a head's gate on one chain, marking a verdict the moment it is heard; a start from before the pending words were last set is not the current check's.	2026-10-11 03:23:52 +02:00
jschoubben	4254d17322	Say where a pending merge check is: queued since when, then building on which machine (hq issue 446) ... The forge's holder set mesh/merge-gate pending as "the mesh is mapping this head onto its module graph" and nothing changed it until the verdict, so a ten-minute controller check read as a stalled forge (issue 423). The holder now says the head waits in the build queue since the local time it was announced; mesh-delivery follows the build seat's started event and says the machine building it and since when, never over a verdict the forge holds.	2026-10-11 03:14:06 +02:00