BM2: a test that cannot run says NOT RUN; the level's bound and the install archive reach the tests

The Go build module's level result carries not-run (the SDK reader's NOT RUN
skips), its tests get MESH_TEST_LEVEL_BOUND, the level's bound, from which
mesh-sdk's helpers take the setup bound; a test call naming an install archive
reads it from the artifact store by its reference and unpacks it into the
workspace's tree before go test. check-needs is read from the module's
manifest, on the Go artifact whose path holds the package, and the marker
file goes: the Node build module's manifest declares it on its bundle.

Builds: design 47 H2 §800; H-A-294, H-A-350 DMC-6, H-A-368, H-A-399 (1) (2) (3)
This commit is contained in:
2026-11-22 01:07:45 +01:00
parent 681de09f04
commit c63b4ae31d
14 changed files with 220 additions and 35 deletions
@@ -1,3 +0,0 @@
# Its integration tests copy the Node toolchain the Node build module installed on this node and run node and npm
# (realMachine, build_integration_test.go): they run only where the node holds node-build-node (issue 890).
node-build-node
+3
View File
@@ -211,6 +211,9 @@
"binary": "mesh-build-node",
"loads": [
"mesh-build-node"
],
"check-needs": [
"node-build-node"
]
},
{