Adolfo Delorenzo
fb24e641ce
Some checks failed
CI / Go Tests (push) Has started running
CI / Build Go Binaries (amd64, linux, linux-amd64) (push) Has been cancelled
CI / Build Go Binaries (arm64, linux, linux-arm64) (push) Has been cancelled
CI / Shellcheck (push) Has been cancelled
ARM64 Build / Build generic ARM64 disk image (push) Failing after 14m12s
After v0.3.1 published successfully, run 524 stayed in 'queued' status overall even though all 5 jobs that actually ran completed at success. Cause: the gated build-iso-amd64 job is `if: false` with `runs-on: amd64-linux`. No runner matches `amd64-linux`, so Gitea queued the job indefinitely waiting for one. The `if:` expression is only evaluated when a runner actually picks up the job, so the skip never fires. Switch the runs-on to `ubuntu-latest` (which our Odroid claims). The runner picks the job up, evaluates `if: false`, marks it `skipped`, and the run as a whole concludes properly. Comment block updated to flag the two lines to flip when a real amd64-linux runner is registered. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>