Gitea Actions runner is not picking up jobs: every run since 2026-08-09 is stuck "Waiting to run" #93

New Issue

clawbot · 2026-08-10T16:08:19+02:00

clawbot commented

2026-08-10 16:08:19 +02:00

Needs you — this is runner-side infrastructure, not something reachable from the repo.

Symptom

Every workflow run queued today is stuck in pending / "Waiting to run" and has never started:

run 17, queued 15:56 on 803b1e6 (head of the golangci-lint unit, before merge)
run 18, queued 16:06 on de47670 (current next)

The last run that actually executed was on 2026-08-09 against 3bfbb3f — check / check (push), success in 37s. Nothing has run since.

I cannot diagnose further from here: GET /repos/sneak/mfer/actions/runs returns 403 user should be the owner of the repo for clawbot, so I can read commit statuses but not run or job detail.

Why it matters

.gitea/workflows/check.yml runs script/cibuild, and that is the only automated gate on this repo. While the runner is down:

No commit can show a green check, including everything landing on next.
The merge-ready signal on the milestone PR rests entirely on gates observed by hand in worker clones rather than on CI.

I am still gating every unit before it lands on next — make check plus a cache-defeated docker build reproducing CI's exact command — and recording the observed output per unit. So the work is verified; it is just not verified by CI, and that distinction should not persist quietly.

Definition of done

The runner is registered, online, and picking up jobs for this repo.
Runs 17 and 18 either execute or are superseded by a run that does, and next shows a real status.
If the runner is intentionally retired, say so and I will open a unit to remove the workflow rather than leave a permanently-pending check on every commit.

Optional and separate: granting clawbot read access to the Actions API for this repo would let me diagnose this class of problem without involving you.

Needs you — this is runner-side infrastructure, not something reachable from the repo. ## Symptom Every workflow run queued today is stuck in `pending` / "Waiting to run" and has never started: - run 17, queued 15:56 on `803b1e6` (head of the golangci-lint unit, before merge) - run 18, queued 16:06 on `de47670` (current `next`) The last run that actually executed was on 2026-08-09 against `3bfbb3f` — `check / check (push)`, success in 37s. Nothing has run since. I cannot diagnose further from here: `GET /repos/sneak/mfer/actions/runs` returns 403 `user should be the owner of the repo` for `clawbot`, so I can read commit statuses but not run or job detail. ## Why it matters `.gitea/workflows/check.yml` runs `script/cibuild`, and that is the only automated gate on this repo. While the runner is down: - No commit can show a green check, including everything landing on `next`. - The `merge-ready` signal on the milestone PR rests entirely on gates observed by hand in worker clones rather than on CI. I am still gating every unit before it lands on `next` — `make check` plus a cache-defeated `docker build` reproducing CI's exact command — and recording the observed output per unit. So the work is verified; it is just not verified *by CI*, and that distinction should not persist quietly. ## Definition of done - The runner is registered, online, and picking up jobs for this repo. - Runs 17 and 18 either execute or are superseded by a run that does, and `next` shows a real status. - If the runner is intentionally retired, say so and I will open a unit to remove the workflow rather than leave a permanently-pending check on every commit. Optional and separate: granting `clawbot` read access to the Actions API for this repo would let me diagnose this class of problem without involving you.

sneak was assigned by clawbot

2026-08-10 16:08:19 +02:00

clawbot referenced this issue

2026-08-10 16:15:58 +02:00

Configure prettier and make fmt-check cover markdown (closes #69) #88

clawbot referenced this issue

2026-08-10 16:17:01 +02:00

1.0.0 milestone #92

Sign in to join this conversation.