klipper-firmware CI still dead: per-repo runner never registered (run 5644 waiting since 2026-08-14T00:43Z) #79

New issue

Closed

opened 2026-08-14 09:31:04 +00:00 by Mark · 0 comments

Mark commented

2026-08-14 09:31:04 +00:00

Owner

Summary

Post-deploy probe of closed issue #78 (kanban card t_86cbfbe7) found that klipper-firmware still has NO per-repo Forgejo Actions runner. Issue #78 explicitly named klipper-firmware (0/131) as affected, but the per-repo runner for it was never registered/started. CI for klipper-firmware remains dead.

Evidence

Newest CI run id=5644 (push, commit 06e4d1a0 "fix(ci): remove klipper3d-deploy workflow from .github and .forgejo; closes #2")
- created: 2026-08-14T00:43:33Z
- status: waiting, started=1970-01-01T00:00:00Z (never picked up)
- URL: https://forgejo.tail018ac4.ts.net/Mark/klipper-firmware/actions/runs/135
On blackhole host: no runner dir exists (ls -d ~/forgejo-runner-klipper* → nothing)
Related: even the #78 fix commit's own CI run (Mark/infrastructure run id=5661, commit 36f01bd6) is waiting/never picked up — no online runner claims infrastructure repo jobs either.

Steps to reproduce

On blackhole: ls -d ~/forgejo-runner-* → no klipper-firmware entry.
Forgejo UI → Mark/klipper-firmware → Actions → run 5644 shows "waiting", started=1970, no online runner.
Push any commit to Mark/klipper-firmware → every run sits waiting until cancelled.

Expected

After the #78 fix, every affected Mark repo (including klipper-firmware, explicitly named in #78) has a live per-repo runner and CI dispatches within seconds of push.

Actual

klipper-firmware has no runner registered at all; run 5644 has been waiting since 2026-08-14T00:43:33Z.

Action needed

Register and start a per-repo runner for klipper-firmware (scripts/forgejo-runner-per-repo.sh documents the flow: GET the repo registration token, forgejo-runner register, start daemon), then verify a fresh push dispatches within seconds.

Filed by reporter from kanban card t_86cbfbe7 (probe of closed issue #78).

## Summary Post-deploy probe of closed issue #78 (kanban card t_86cbfbe7) found that **klipper-firmware still has NO per-repo Forgejo Actions runner**. Issue #78 explicitly named klipper-firmware (0/131) as affected, but the per-repo runner for it was never registered/started. CI for klipper-firmware remains dead. ## Evidence - Newest CI run **id=5644** (push, commit `06e4d1a0` "fix(ci): remove klipper3d-deploy workflow from .github and .forgejo; closes #2") - created: 2026-08-14T00:43:33Z - status: `waiting`, started=1970-01-01T00:00:00Z (never picked up) - URL: https://forgejo.tail018ac4.ts.net/Mark/klipper-firmware/actions/runs/135 - On blackhole host: no runner dir exists (`ls -d ~/forgejo-runner-klipper*` → nothing) - Related: even the #78 fix commit's own CI run (Mark/infrastructure run id=5661, commit `36f01bd6`) is `waiting`/never picked up — no online runner claims infrastructure repo jobs either. ## Steps to reproduce 1. On blackhole: `ls -d ~/forgejo-runner-*` → no klipper-firmware entry. 2. Forgejo UI → Mark/klipper-firmware → Actions → run 5644 shows "waiting", started=1970, no online runner. 3. Push any commit to Mark/klipper-firmware → every run sits `waiting` until cancelled. ## Expected After the #78 fix, every affected Mark repo (including klipper-firmware, explicitly named in #78) has a live per-repo runner and CI dispatches within seconds of push. ## Actual klipper-firmware has no runner registered at all; run 5644 has been waiting since 2026-08-14T00:43:33Z. ## Action needed Register and start a per-repo runner for klipper-firmware (scripts/forgejo-runner-per-repo.sh documents the flow: GET the repo registration token, forgejo-runner register, start daemon), then verify a fresh push dispatches within seconds. Filed by reporter from kanban card t_86cbfbe7 (probe of closed issue #78).