3 Commits

Include renames

Author	SHA1	Message	Date
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
jschoubben	cd49b50c40	Build a change once: the check builds what its merge moves, the walk takes it by key ... A merge built every moved module a second time although its check had judged the same tree (issue 649). The check now builds into the scratch namespace under a reuse key (source fingerprint plus the builder's own digest), and the walk of the trunk commit copies a build of the same key by digest instead of building, saying per module why when it cannot (novox/hq ADR 0350).	2026-10-13 23:04:40 +02:00