novox/mesh-catalog
18
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Build modules run at most as many steps as their node's build CPU gives, and say a check's phases

Browse Source 
Each of mesh-build-go, -node and -image declares cores-per-step (6, 2, 2) and hands it to the
SDK puller, which bounds the configured capacity by floor(slice quota cores / cores-per-step),
read live; thread limits and the status tools follow the effective capacity (issue 1806's
follow-up: three Go checks on shanks' 12-core slice starved past the 30-minute step bound).
mesh-build-go says its lint and test phases with the ask id (issue 1890).
This commit is contained in:
jschoubben
2026-10-26 19:55:31 +01:00
parent da29f77b10
commit 245143d948
21 changed files with 102 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files
modules/mesh-build-node/go.mod
+1 -1
View File
@@ -3,7 +3,7 @@ module meshbuildnode
go 1.26.0
require (
git.novox.be/novox/mesh-sdk/go v0.1.14-0.20261026142629-ff81bdf8cc8f
git.novox.be/novox/mesh-sdk/go v0.1.14-0.20261026185254-02f50bd9d642
github.com/distribution/distribution/v3 v3.1.2
github.com/nats-io/nats.go v1.54.0
)