From 91f3be844aaeea153e04b47c33bd81562b063d79 Mon Sep 17 00:00:00 2001 From: bong-water-water-bong Date: Mon, 9 Nov 2026 10:39:24 -0400 Subject: [PATCH] hw-gate: link the runner recipe where the page names the runners docs/ci-runners.md arrived in #1609 and nothing links it - measured by extracting every .md link in docs/, README.md, the blog and the landing pages - and it has no entry in the site's sidebar either, so its only route in was the auto-generated docs index. docs/hw-gate.md is its natural home: the page's subject is a job that runs on the box's own runners, and it names two of them (strixhalo-engine for the gate, strixhalo-bench for the bench jobs) while assuming they exist. One sentence now says where they come from - the restart policy, the cgroup ceiling and the dedicated user - and links the recipe, plus the 2026-11-08 outage the missing restart policy turned into four hours (ci-runners.md:33-48). No new claim: the recipe's parts are #1609's own description, and MemoryHigh/MemoryMax and OOMPolicy are the guard it names at ci-runners.md:70,90,245. --- docs/hw-gate.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/hw-gate.md b/docs/hw-gate.md index 9ad7bfeb2..b5da6d999 100644 --- a/docs/hw-gate.md +++ b/docs/hw-gate.md @@ -30,6 +30,11 @@ and #370. The hardware gate checks every HRX pin bump, and every PR that asks fo - **By hand.** Actions -> hw-gate -> Run workflow, with a ref (a branch, tag, SHA or `pull/N/head`). The run posts the commit status `hw-gate` on the commit it checked, so a PR shows the result. +Both runners this page names - `strixhalo-engine` here and `strixhalo-bench` for the bench jobs - are installed and +supervised as one recipe: a restart policy, an OOM guard and a dedicated user, so a build that dies cannot take the box's +other jobs with it. That install, and the 2026-11-08 outage that the missing restart policy turned into four hours, are in +[ci-runners.md](ci-runners.md). + A pin bump raised **by hand** must therefore do one of the two automated things: name its branch `bump-hrx/` (the `bump-hrx` workflow's own convention) or add the `hw-gate` label. Neither is a formality - without one the job does not run and the PR simply reads `hw_gate: skipping`, which looks like a pass in a list of ticks (engine#672: a