BFE Engineering
c756622c96
The repo's documentation framed it as a support repo for one product (WardenOS). Since going public the real audience is anyone with a Luckfox Pico 86 Panel: a maintained 6.18 kernel, an off-device development loop, and a device simulator that exist nowhere else for this board. Reframe the README and top-level docs board-first, with WardenOS documented as the downstream consumer it is (ADR-0008). Also an editorial pass over the whole doc set: - every H1/H2 is now a short title, not a sentence (ADRs, qemu/, patches/, drivers/, architecture, NPU feasibility, config-lint, payload); workflow flowchart titles fixed at the source in tools/flowgen.py and regenerated with fresh bench numbers - README Quick Start commands verified against the scripts; requirements corrected (curl, bare python, gcc >= 14) and the MC/DC gate added as a step (run green locally on gcc 14.2) - dropped the 'needs python (not python3)' vendor dig: build-kernel.sh inherited the same requirement (filed #10 to remove it) - glossed MC/DC and HPMCU on first use; marked the tests/uboot-ab reference as flare-edge; deduplicated the three-simulator list into the root README table
24 lines
1.2 KiB
Markdown
24 lines
1.2 KiB
Markdown
# ADR 0004 — Self-Hosted Runner
|
|
|
|
**Status:** Superseded in part by ADR-0007 (2026-08-30) — `kernel-build` moved
|
|
to GitHub-hosted runners for the public repo and the self-hosted registration
|
|
is retired. Original decision below, kept for the record. (2026-08-25.)
|
|
|
|
## Context
|
|
The heavy kernel/firmware build needs the SDK toolchain and Buildroot's baked-in
|
|
absolute paths — impractical on GitHub-hosted runners. flare-edge already builds on
|
|
a repo-scoped self-hosted runner on `bfe-mpc-0640` (label `flare-edge`); a repo-scoped
|
|
registration cannot be shared across repos by label alone.
|
|
|
|
## Decision
|
|
Register a **third repo-scoped runner instance** on `bfe-mpc-0640`, label
|
|
`warden-sdk` (its own repo-scoped runner systemd unit, own
|
|
`CPUQuota=400%`/`MemoryMax=6G` drop-in). Only the heavy `kernel-build` job uses
|
|
`runs-on: [self-hosted, warden-sdk]`; all host-testable jobs (tests, coverage, MC/DC,
|
|
benchmarks, badges, patches-apply) run on GitHub-hosted runners.
|
|
|
|
## Consequences
|
|
- Isolated from the flare backend + flare-edge CI already on that host (cgroup-capped).
|
|
- Runner setup + host build deps + the project-local `python` venv documented in
|
|
`docs/ci-cd.md`, mirroring flare-edge's.
|