H4: the builder machine of the toolchain tests has the tool runner's seat-settle-delay (issue 1966; mesh-catalog's issue 1748, ADR 0664 §5)
Since mesh-catalog 6b8e7fc6 the build modules ask the capability seat-settle-delay of the machine, so on the stand-in builder without it mesh-build-go and mesh-build-node were left out as unhostable and both toolchain tests failed against the catalogue's main, on mesh-host's trunk as on this group's head. Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
This commit is contained in:
@@ -10,10 +10,11 @@ import (
|
||||
// builderNode is a machine that can run a build module: the package manager and user namespaces it asks of
|
||||
// the machine, and the forge account (mesh-scope, provided by the forge) and the artifact store the build
|
||||
// modules publish to (ADR 0513, provided by distribution) stood in for, and node-tools, the tool runner they pull their
|
||||
// asks through (mesh-catalog issue 1911; mesh-tools' module, not in the catalogue).
|
||||
// asks through (mesh-catalog issue 1911; mesh-tools' module, not in the catalogue), with the tool runner's
|
||||
// seat-settle-delay the build modules ask of it since issue 1748 (ADR 0664 §5).
|
||||
func builderNode() mcat.Node {
|
||||
return mcat.Node{Name: "builder", Site: "house",
|
||||
Capabilities: map[string]bool{"package-manager": true, "user-namespaces": true}}
|
||||
Capabilities: map[string]bool{"package-manager": true, "user-namespaces": true, "seat-settle-delay": true}}
|
||||
}
|
||||
|
||||
func toolchainShelf(t *testing.T) map[string]mcat.Manifest {
|
||||
|
||||
Reference in New Issue
Block a user