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

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

									
										modules/mesh-build-node/files/settings.json
									
		+2
		-1
	
												View File
												
				@@ -1,3 +1,4 @@

				{

				  "capacity": "shanks=3,ace=2,g14=0,novox=0"

				  "capacity": "shanks=3,ace=2,g14=0,novox=0",

				  "cores-per-step": 2

				}