A fresh check keeps a build whose key is unchanged instead of building it again (hq issue 703) #328

Merged

mesh-admin merged 3 commits from fix/703-a-fresh-check-keeps-an-unchanged-build into main 2026-10-14 08:15:56 +00:00

Conversation 4 Commits 3 Files Changed 16

+623 -54

3 Commits

Author	SHA1	Message	Date
jschoubben	c707bf18d8	Say which check made a build the walk does not take, and test the merged heads ... A build of another pull request or of a head the forge did not merge is in no verdict the walk is handed; the walk now names the check that made it, so its "built:" line says which head it was (novox/hq issue 703).	2026-10-14 10:05:31 +02:00
jschoubben	060f2a9ca5	Build for the merge from a copy its tests never touch, and keep or take only the same head's build ... The gate and the repository's check mount the workspace read-write, so a build from that tree could hold what the tests wrote under a key that describes the merge. A check now clones the merge outside the workspace before anything of the change runs, and builds from that. A check keeps, and a walk takes, only a build an earlier check of the same pull request at the same head made: another pull request's build, or an earlier head's, is never registered. The walk reads the verdicts once (novox/hq issue 703, review of #328).	2026-10-14 09:56:23 +02:00
jschoubben	1666747a22	Keep a check build whose key is unchanged instead of building it again ... A fresh check asked when only the trunk moved rebuilt every image, though the reuse key said nothing it is built from changed: a controller check took about 12 minutes instead of 5.5. The check now keeps a build kept under its key when a verdict of the build seat names that key and every digest, names it as the build's own check so a walk takes it, and the cleanup keeps it while any check names it (novox/hq issue 703).	2026-10-14 09:41:39 +02:00