hanzoai/hanzo.network
2
0
Fork 0
mirror of https://github.com/hanzoai/hanzo.network.git synced 2026-09-25 02:14:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

the job asks for its runner the way the fleet answers

Browse Source 
runs-on was a bare scalar. Jobs written that way queue and are never
picked up — link and quest have waited since 10 August, painter since the
5th, none of them with a single success — while repos writing the same
label as a sequence drain within seconds of a push on the same fleet.

Same label, same runners, different shape. It fails silently: nothing errors,
the job simply never starts, so the lane looks configured and does nothing.
This commit is contained in:
zeekay
2026-08-29 12:59:27 -07:00
parent 8d0ea3e622
commit bfc601c0ac
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.hanzo/workflows/deploy.yml
+1 -1
View File
@@ -27,7 +27,7 @@ jobs:
# retried ~520 times across 10 runners). An unmatched label is not an
# error here, it is silence: the job queues until the 24h timeout, so this
# deploy has never produced an image and nothing ever said so.
runs-on: hanzo-build-linux-amd64
runs-on: [hanzo-build-linux-amd64]
timeout-minutes: 30
steps:
- uses: actions/checkout@v4