ci: give t3code two CPUs and keep CI on one #107

Merged

gecko merged 1 commit from t3/increase-t3code-cpus into main

2026-11-03 21:14:00 +00:00

gecko commented

2026-11-03 20:51:26 +00:00

Owner

Summary

Keep the T3 Code CPU/memory drop-in host-local and remove ops/ci/t3code-service.conf from the repository. The live drop-in at /etc/systemd/system/t3code.service.d/10-ci-isolation.conf remains installed and pins t3code.service to CPUs 1-2.
Shrink mcbot-ci.slice from CPUs 0-1 to CPU 0 with a 100% quota, keeping the CI and T3 CPU sets disjoint.
Keep both repository runner processes registered as overflow capacity. No runner count reduction was needed; concurrent CI jobs share the remaining CPU.

Validation

./scripts/ci-preflight.sh passed.
Live nproc is 2 inside the T3 service cgroup and 1 inside the CI slice.
systemctl --failed reports no failed units; Docker, containerd, both runners and t3code.service are active.
Tested commit: 72e328c.

## Summary - Keep the T3 Code CPU/memory drop-in host-local and remove `ops/ci/t3code-service.conf` from the repository. The live drop-in at `/etc/systemd/system/t3code.service.d/10-ci-isolation.conf` remains installed and pins `t3code.service` to CPUs 1-2. - Shrink `mcbot-ci.slice` from CPUs 0-1 to CPU 0 with a 100% quota, keeping the CI and T3 CPU sets disjoint. - Keep both repository runner processes registered as overflow capacity. No runner count reduction was needed; concurrent CI jobs share the remaining CPU. ## Validation - `./scripts/ci-preflight.sh` passed. - Live `nproc` is 2 inside the T3 service cgroup and 1 inside the CI slice. - `systemctl --failed` reports no failed units; Docker, containerd, both runners and `t3code.service` are active. - Tested commit: 72e328c.

gecko added 1 commit

2026-11-03 20:51:26 +00:00

ci: give t3code two CPUs and keep CI on one

build / Java 25 build (pull_request) Successful in 1m42s

Details

1f1f8f7674

Rebalance the three-CPU development host: t3code.service and its agent shells move from CPU 2 alone to CPUs 1-2, while mcbot-ci.slice drops from CPUs 0-1 to CPU 0 with a 100% quota. Both repository runner processes stay registered as overflow capacity; concurrent jobs share the remaining CPU.

gecko commented

2026-11-03 20:55:14 +00:00

Author

Owner

CI passed on 1f1f8f7: Java 25 build, success in 1m42s — https://git.glitched.systems/gecko/mcbot/actions/runs/884

CI passed on 1f1f8f7: Java 25 build, success in 1m42s — https://git.glitched.systems/gecko/mcbot/actions/runs/884

gecko force-pushed t3/increase-t3code-cpus from 1f1f8f7674

build / Java 25 build (pull_request) Successful in 1m42s

Details

to 72e328cecb

build / Java 25 build (pull_request) Successful in 3m33s

Details