docs(ci-cd): runner installed + online, kernel-build verified (2026-08-25)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017wB8KB3MMQztRDXCMCkPrf
This commit is contained in:
BFE Engineering
2026-08-25 17:40:24 -06:00
co-authored by Claude Opus 4.8
parent 40a61b5e62
commit 82b8bc91bb
+8 -4
View File
@@ -18,10 +18,14 @@
A **third** repo-scoped runner instance on `bfe-mpc-0640` (alongside `flare` and A **third** repo-scoped runner instance on `bfe-mpc-0640` (alongside `flare` and
`flare-edge`), registered with the label **`warden-sdk`** as `flare-edge`), registered with the label **`warden-sdk`** as
`bfe-mpc-0640-warden-sdk`, in `~/actions-runner-warden-sdk`. The registration is `bfe-mpc-0640-warden-sdk`, in `~/actions-runner-warden-sdk`.
done. **Steps 12 below need `user`'s sudo on 0640** (systemd service + cgroup —
not automatable from the dev box); **steps 34 are handled inside the workflow**, so > **INSTALLED + ONLINE (2026-08-25).** The runner is a running systemd service
the runner host needs no manual toolchain/python setup. > (`actions.runner.bfe-noah-warden-sdk.bfe-mpc-0640-warden-sdk.service`, `enabled`,
> cgroup-capped `CPUQuota=400%`/`MemoryMax=6G`) and `kernel-build` has been verified
> end-to-end (RV1106 6.18.46 → `zImage` 8.25 MB + `rv1106-warden.dtb`). Steps 12
> below are the record of that install (they needed `user`'s sudo on 0640); steps
> 34 are handled inside the workflow, so the host needs no manual toolchain/python.
1. **Install as a service** (persistence): `cd ~/actions-runner-warden-sdk && 1. **Install as a service** (persistence): `cd ~/actions-runner-warden-sdk &&
sudo ./svc.sh install user && sudo ./svc.sh start`. Until then the runner is sudo ./svc.sh install user && sudo ./svc.sh start`. Until then the runner is