Forgejo Actions CI has not run on main pushes for 18 days #297

New issue

Closed

opened 2026-06-12 06:37:06 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-12 06:37:06 +00:00

Owner

lint.yml (workflow "CI") triggers on every push to main, but the newest CI run is 18 days old (#437, the dind-over-tcp runner fix) while many pushes landed since - the ser8/authorized-keys merge, the opencode work, and today's tailscale commits all produced no runs. TruffleHog and Dependency Graph workflows show the same gap (Dependency Graph ran 1h ago, so Forgejo itself is alive - this looks runner-side). Check the two Forgejo Actions runner deployments on kai-server (deploy/forgejo-runner.yml), they may have been wedged since the dind change in #437.

`lint.yml` (workflow "CI") triggers on every push to `main`, but the newest CI run is 18 days old (#437, the dind-over-tcp runner fix) while many pushes landed since - the ser8/authorized-keys merge, the opencode work, and today's tailscale commits all produced no runs. TruffleHog and Dependency Graph workflows show the same gap (Dependency Graph ran 1h ago, so Forgejo itself is alive - this looks runner-side). Check the two Forgejo Actions runner deployments on kai-server (`deploy/forgejo-runner.yml`), they may have been wedged since the dind change in #437.

coilysiren referenced this issue

2026-06-12 11:13:08 +00:00

k3s.service pkill -9 containerd-shim orphans container payloads on every restart, causing recurring lock-blocked crashloops (CI, o11y) #311

coilysiren

2026-06-17 07:06:21 +00:00