CI workflow: go test + go build on push #2

Closed
opened 2026-09-29 01:55:12 +00:00 by Winnie · 3 comments
Owner
No description provided.
Author
Owner

Workflow file is in the repo and the run is queued, but no runner picks it up: the existing runners are scoped elsewhere and a repo-scoped runner for Winnie/bankwars is being registered. In progress.

Workflow file is in the repo and the run is queued, but no runner picks it up: the existing runners are scoped elsewhere and a repo-scoped runner for Winnie/bankwars is being registered. In progress.
Author
Owner

Workflow file is in the repo and correct (go vet + go test on push). Runner situation: Forgejo 16.0.3 accepts user-level runner registration (Register returns 200 and a runner record) but Declare is rejected as unregistered, so the job sits waiting. Existing instance runners serve other scopes. This needs either a Forgejo upgrade or an admin-scoped runner. Blocked on infra, not on the workflow.

Workflow file is in the repo and correct (go vet + go test on push). Runner situation: Forgejo 16.0.3 accepts user-level runner registration (Register returns 200 and a runner record) but Declare is rejected as unregistered, so the job sits waiting. Existing instance runners serve other scopes. This needs either a Forgejo upgrade or an admin-scoped runner. Blocked on infra, not on the workflow.
Author
Owner

Fixed, CI is green on the regular runners. The real problem was mine, not the runners: the workflow asked for the label docker:docker://debian:trixie while the instance runners declare docker, so every job waited forever. Changed to runs-on: docker, and added a setup step that installs git (the debian:trixie job image has no git, which broke checkout on the first picked-up run). The extra runner I built is deleted, container and registrations both. Run 18 on master: success.

Fixed, CI is green on the regular runners. The real problem was mine, not the runners: the workflow asked for the label docker:docker://debian:trixie while the instance runners declare docker, so every job waited forever. Changed to runs-on: docker, and added a setup step that installs git (the debian:trixie job image has no git, which broke checkout on the first picked-up run). The extra runner I built is deleted, container and registrations both. Run 18 on master: success.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Winnie/bankwars#2
No description provided.