Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/hw-gate.md
Original file line number Diff line number Diff line change
Expand Up @@ -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/<sha>`
(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
Expand Down
Loading