9 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	a01715ddf5	Skip the Node build module's toolchain tests by name where no Node toolchain is installed, instead of installing one from the registry in a level that has no network; merge three tests that share one fixture ... On ace, which holds no Node build module, five integration tests each spent 70 s in npm's network retries and failed every mesh-catalog check run there (five verdicts since 00:07). The tests now copy the node's installed toolchain or are skipped as NOT RUN; the registry is never reached. Three tests sharing the fixture are one, so the toolchain is copied three times instead of five (10 integration tests in the module, now 8).	2026-10-26 12:05:09 +01:00
jschoubben	2ebcb18097	realMachine: a change carrying a lock no release has installed runs with the toolchain installed last, and says so, so a lock change is not refused by its own check (issue 1891, ADR 0533 §3)	2026-10-23 11:23:11 +02:00
jschoubben	00e54d46d7	Give the integration level the node's installed Node toolchains read-only, so the Node build module's tests build offline (issue 1891, ADR 0533) ... mesh-build-go binds /var/lib/mesh-build-node-cache/toolchain read-only into the integration level's one shut-off process when it is there; the unit level never. mesh-build-node opens its installed toolchains to other accounts (folders 0755, files 0644, writable by its owner alone; its cache 0711, so the npm cache beside them stays its own), and realMachine copies the toolchain of its own lock from there instead of npm ci from the registry, which the level cannot reach.	2026-10-23 11:22:05 +02:00
jschoubben	0786408109	Say loudly, not fail, where a check has no bubblewrap to run a build module's shut-off steps (issue 1309) ... build-agent's check container has no bwrap; the build nodes, where the checker runs from R4e, do. The sibling test and the real Node build skip naming it, and the pull-head pin test still runs its fetch half and skips only the shut-off build.	2026-10-22 19:04:24 +02:00
jschoubben	3a25b6e1f8	mesh-build-node: push each done bundle to the artifact store from its own process and answer its reference (issue 1587, S5-S8, ADR 0498 §1 §2, lead decision L9) ... After the build ended the module pushes the packed bundle with mesh-sdk's PushBlob under <module>/<artifact> by its digest, a candidate's as a trunk build's, and the step answers artifact-store://<module>/<artifact>/blobs/<digest> instead of the archive's path. A push that fails fails the step not stored: <artifact>: <the store's words>; the packed bytes are never written to the node. The manifest requires artifact-store and places its address.	2026-10-22 18:25:14 +02:00
jschoubben	22992da15d	mesh-build-node: emit a package that builds before its tests, so tests importing its own output find it (issue 1869, part of issue 1309's run step) ... A package with a build or prepare script and a tsconfig.json is built with tsc -p . in the shut-off run step, at both levels, instead of the --noEmit type-check; the fetch's --ignore-scripts never runs those scripts. mesh-sdk's tests import ../dist and failed ERR_MODULE_NOT_FOUND. The result names the step build.	2026-10-22 18:23:25 +02:00
mesh-tools	bcee61edf7	Skip, loudly, a build module's real-toolchain test where the check's image lacks the tool; it is proven live on a build node (issues 1486, 1490)	2026-10-20 21:19:15 +00:00
mesh-tools	983a6c39c8	Ship the Node build module's toolchain lock as an archive, not a template naming hosts (issue 1488)	2026-10-20 21:15:56 +00:00
mesh-tools	1d6c905407	Add the Node build module's workspace and the tests of its build and test steps (issues 1490, 1491), part 18 of 19	2026-10-20 21:04:12 +00:00