mirror of
https://github.com/hanzoai/hanzo.network.git
synced 2026-09-25 02:14:24 +00:00
ci: name a pool the fleet actually advertises
The deploy job asked for `ubuntu-latest`. This file lives in .hanzo/workflows, which GitHub never reads -- git.hanzo.ai is the only thing that can run it, and the fleet advertises no generic ubuntu-* label. That is deliberate and recorded in the runner ConfigMap: ~1400 mirrored upstream forks all ask for ubuntu-latest, and the forge errors rather than skipping a job it cannot place, so one bad job was retried ~520 times across 10 runners. An unmatched label is not a failure here, it is silence -- the job queues until the 24h timeout. So this deploy has never produced an image, and nothing ever said so. Same class as the playground regression, found by checking every .hanzo/workflows file against the labels the runner ConfigMap actually declares rather than against the ones I assumed. hanzo-build-linux-amd64 is registered (verified against cm/git-runner-config). Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
@@ -20,7 +20,14 @@ concurrency:
|
||||
|
||||
jobs:
|
||||
image:
|
||||
runs-on: ubuntu-latest
|
||||
# hanzo-build-linux-amd64, not ubuntu-latest. This file lives in
|
||||
# .hanzo/workflows, which GitHub never reads -- git.hanzo.ai is the only
|
||||
# thing that can run it, and the fleet deliberately advertises no generic
|
||||
# ubuntu-* label (~1400 mirrored forks all ask for it; one bad job was
|
||||
# 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
|
||||
timeout-minutes: 30
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
|
||||
Reference in New Issue
Block a user