The Apple leg asked for a label the runners do not advertise

runs-on named hanzo-build-macos-arm64. RUNNERS.md registers the Apple pool as
hanzo-build-darwin-arm64 (with metal, m4max and dbc alongside it), and a job
asking for a label nobody carries is accepted and queued rather than refused —
so this leg has been sitting in a queue while its sibling job, on a registered
label, ran and made the repo look like it had CI.

Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
2026-09-02 02:25:32 -07:00
co-authored by Hanzo Dev
parent 1563b90d51
commit f310c6db24
+5 -1
View File
@@ -16,7 +16,11 @@ jobs:
- run: cargo clippy --all-targets -- -D warnings
- run: cargo test --all-targets
metal:
runs-on: hanzo-build-macos-arm64
# hanzo-build-darwin-arm64: the label RUNNERS.md registers for the
# Apple pool. hanzo-build-macos-arm64 is not one it lists, and a job
# asking for a label no runner advertises queues forever rather than
# failing — so the repo keeps looking like it has CI on this leg.
runs-on: hanzo-build-darwin-arm64
timeout-minutes: 60
steps:
- uses: actions/checkout@v6