novox/mesh-controller
18
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Name the build slice without a dash so it sits beside user.slice, and restart it when its limits change (issue 1798)
mesh/merge-gate building on ace since 00:57
mesh/delivery superseded: a newer head of the same pull request
Details
mesh/check failed: integration: github.com/novox/mesh-controller/internal/identity.TestACertificateChainsToTheMeshsOwnAuthority: authority_test.go:45:…

Browse Source
This commit is contained in:
jschoubben
2026-10-22 00:56:48 +02:00
parent 37119ea31f
commit b174d743c0
5 changed files with 29 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
modules/build-agent/files/build-agent.env
+1 -1
View File
@@ -6,4 +6,4 @@ MESH_NPM_TOKEN_FILE=/run/mesh/package-registry.secret
MESH_GENESIS_PACKAGE_REGISTRY=/run/mesh/genesis-package-registry.json
MESH_WORKSPACE=${dir:workspace}
MESH_JUDGE_CACHE=${dir:judge-cache}
MESH_BUILD_CGROUP_PARENT=mesh-build.slice
MESH_BUILD_CGROUP_PARENT=meshbuild.slice
modules/build-agent/files/mesh-build.slice → modules/build-agent/files/meshbuild.slice
+1 -1
View File
@@ -1,7 +1,7 @@
# Managed by the mesh (module build-agent). Replaced on every push; edit the module's settings instead.
#
# Everything a build or check starts on this machine runs in this slice (novox/hq issue 1798): the build
# agent starts every container with --cgroup-parent=mesh-build.slice. The weights only bind while the machine
# agent starts every container with --cgroup-parent=meshbuild.slice. The weights only bind while the machine
# is busy, so an idle machine still builds at full speed; the memory limits are the part that always binds.
[Slice]
CPUWeight=${setting:cpu-weight}