Forgejo Actions runner idle since 2026-05-31: no CI run for pushes to main #288

New issue

Closed

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

coilysiren commented

2026-06-12 05:40:12 +00:00

Owner

Pushing 46a3505 (merge of the GitHub mirror divergence) to canonical main on 2026-06-11 produced no Forgejo Actions run. The newest workflow runs on this repo are for 8eb4058 dated 2026-05-31, so the in-cluster forgejo-runner appears to have stopped picking up jobs roughly 11 days ago.

Observed via GET /api/v1/repos/coilyco-flight-deck/infrastructure/actions/tasks:

8eb4058 lint success created=2026-05-31T02:27:37Z branch=main
a09cb3f lint success created=2026-05-30T17:36:58Z branch=main

Next steps:

Check the forgejo-runner deployment on kai-server (deploy/forgejo-runner.yml, tap-writer runner workingDir trap in docs/k3s-deploy-notes.md).
Once the runner is back, confirm 46a3505 (or the then-current main tip) gets a lint + secret-scan run.

Context: the push itself landed clean on both Forgejo and the GitHub mirror, and the full local pre-commit suite (which mirrors the CI lint job) passed. This issue is only about the missing CI execution.

Pushing `46a3505` (merge of the GitHub mirror divergence) to canonical `main` on 2026-06-11 produced no Forgejo Actions run. The newest workflow runs on this repo are for `8eb4058` dated 2026-05-31, so the in-cluster forgejo-runner appears to have stopped picking up jobs roughly 11 days ago. Observed via `GET /api/v1/repos/coilyco-flight-deck/infrastructure/actions/tasks`: ``` 8eb4058 lint success created=2026-05-31T02:27:37Z branch=main a09cb3f lint success created=2026-05-30T17:36:58Z branch=main ``` Next steps: * Check the forgejo-runner deployment on kai-server (`deploy/forgejo-runner.yml`, tap-writer runner workingDir trap in docs/k3s-deploy-notes.md). * Once the runner is back, confirm `46a3505` (or the then-current `main` tip) gets a lint + secret-scan run. Context: the push itself landed clean on both Forgejo and the GitHub mirror, and the full local pre-commit suite (which mirrors the CI lint job) passed. This issue is only about the missing CI execution.

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:09 +00:00

closed this issue
added the
priority
P0
label

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

coilyco-flight-deck/infrastructure#288

No description provided.

Rows
Columns