Say how a check's clones are chosen and what the captured copy carries (issue 432 review)

2026-10-11 03:00:28 +02:00
parent eb72075104
commit 68fbd99e89
2 changed files with 10 additions and 1 deletions
@@ -8,7 +8,12 @@
 //   - In a merge check, the build seat clones each core repository beside the one checked (the catalogue
 //     at its main, the node-engine at the commit the mesh runs) and says where in MESH_CHECK_BESIDE. A
 //     test judges against those clones, so agreement with the other repository is checked where
-//     `mesh/repo-check` runs; a repository missing there fails the test, never skips it.
+//     `mesh/repo-check` runs; a repository missing there fails the test, never skips it. Which clones a
+//     check gets is chosen from the inventory: mesh-catalog by the source of the `nats` module, mesh-host
+//     by the source of `mesh-host`. In a mesh where either module has no source repository nothing is
+//     cloned, and these tests fail loudly with "not beside this check": a cause in the setup, not in the
+//     change. And in a delivery group that holds a mesh-catalog pull request, these tests read the
+//     catalogue's main, not the group's head.
 //   - Anywhere else, the test judges against the copy captured in this repository's testdata/beside, at the
 //     commit testdata/beside/CAPTURED names. Never against a developer's own checkout: to judge one, set
 //     MESH_CHECK_BESIDE to the directory holding it, as the check does.