Forgejo Actions CI never dispatches on Mark/chainbound — #56 fix never built, deploy-itchbox stale since 2026-06-16 (last success 2026-06-19) #59

New issue

Closed

opened 2026-08-14 07:45:31 +00:00 by Mark · 1 comment

Mark commented

2026-08-14 07:45:31 +00:00

Owner

Forgejo Actions CI is not running for Mark/chainbound. No online runner is picking up this repo's jobs: every push run since 0a1fd93 (2026-08-11) is either cancelled or stuck waiting with started=1970, and the current head 59489d4 has runs 5689 (ci.yml) / 5690 (deploy-itchbox.yml) sitting waiting indefinitely.

Consequence for #56 (chain-anchor modifier anchor, closed 2026-08-14T00:33:08Z): the fix commits fb2b6c2 and 3f79dd4 are on origin/main and pass 329/329 local vitest tests (14 files, incl. the dedicated e2e chain-anchor turn flow test), but neither ever got a CI run — run 5645 (ci.yml) and 5646 (deploy-itchbox.yml) for 3f79dd4 were cancelled without starting, and fb2b6c2 has no run at all. The deploy-itchbox.yml workflow (triggers on every push to main) therefore never rebuilt the deployed game: the last successful deploy is run 4188 (2026-06-16, head 9bb1c90b). The deployed artifact at itchbox does not contain the #56 fix.

Actual: push events create runs that sit waiting indefinitely and get cancelled; last CI success run 4289 (ci.yml, 2026-06-19). Last deploy-itchbox success run 4188 (2026-06-16).
Expected: runs dispatch to an online runner within minutes (pattern: runs 4187/4188/4252/4289 in June).

Likely cause (from prior diagnosis pattern): workflow uses runs-on: ubuntu-latest but no online runner is registered with that label for Mark/chainbound — repo-scoped runners on other repos silently ignore jobs from this repo. Same systemic runner-coverage condition already tracked for Mark/planish#16, Mark/transcriber#136, Mark/nodedesk#55, Mark/kimi_agent_kin_app_sync#160; this issue is the chainbound-specific record. Fix: register a runner for this repo (or use the linux label that the blackhole runner registers) so runs dispatch.

Reproduction:

Push any commit to origin/main.
Watch the Actions tab: both ci.yml and deploy-itchbox.yml runs stay waiting, never get a started_at, then get cancelled (runs 5689/5690 for head 59489d4 are the current example).
Compare: run 4289 (2026-06-19) is the last CI run with a conclusion.

Also noted during probe: http://itchbox.tail018ac4.ts.net was unreachable from the probe host (10s connect timeout), so the deployed artifact could not be spot-checked remotely.

Filed from kanban card t_48c4d9ce (post-deploy probe of Mark/chainbound#56).

Forgejo Actions CI is not running for Mark/chainbound. No online runner is picking up this repo's jobs: every push run since `0a1fd93` (2026-08-11) is either `cancelled` or stuck `waiting` with started=1970, and the current head `59489d4` has runs 5689 (ci.yml) / 5690 (deploy-itchbox.yml) sitting `waiting` indefinitely. Consequence for #56 (chain-anchor modifier anchor, closed 2026-08-14T00:33:08Z): the fix commits `fb2b6c2` and `3f79dd4` are on origin/main and pass 329/329 local vitest tests (14 files, incl. the dedicated e2e `chain-anchor turn flow` test), but **neither ever got a CI run** — run 5645 (ci.yml) and 5646 (deploy-itchbox.yml) for `3f79dd4` were cancelled without starting, and `fb2b6c2` has no run at all. The `deploy-itchbox.yml` workflow (triggers on every push to main) therefore never rebuilt the deployed game: the last successful deploy is run 4188 (2026-06-16, head `9bb1c90b`). The deployed artifact at itchbox does **not** contain the #56 fix. Actual: push events create runs that sit `waiting` indefinitely and get cancelled; last CI success run 4289 (ci.yml, 2026-06-19). Last deploy-itchbox success run 4188 (2026-06-16). Expected: runs dispatch to an online runner within minutes (pattern: runs 4187/4188/4252/4289 in June). Likely cause (from prior diagnosis pattern): workflow uses `runs-on: ubuntu-latest` but no online runner is registered with that label for Mark/chainbound — repo-scoped runners on other repos silently ignore jobs from this repo. Same systemic runner-coverage condition already tracked for Mark/planish#16, Mark/transcriber#136, Mark/nodedesk#55, Mark/kimi_agent_kin_app_sync#160; this issue is the chainbound-specific record. Fix: register a runner for this repo (or use the `linux` label that the blackhole runner registers) so runs dispatch. Reproduction: - Push any commit to origin/main. - Watch the Actions tab: both ci.yml and deploy-itchbox.yml runs stay `waiting`, never get a started_at, then get cancelled (runs 5689/5690 for head 59489d4 are the current example). - Compare: run 4289 (2026-06-19) is the last CI run with a conclusion. Also noted during probe: `http://itchbox.tail018ac4.ts.net` was unreachable from the probe host (10s connect timeout), so the deployed artifact could not be spot-checked remotely. Filed from kanban card t_48c4d9ce (post-deploy probe of Mark/chainbound#56).

Mark added the

bug

label

2026-08-14 07:45:31 +00:00

Mark added the

triage-approved

label

2026-09-15 15:36:49 +00:00

Mark commented

2026-09-18 15:38:12 +00:00

Author

Owner

Closing as stale — the underlying runner-coverage condition has been resolved organically and CI is currently dispatching on Mark/chainbound.

Evidence (live API check 2026-09-18):

Run 7086 (ci.yml, head 7cf0505 'fix #61') — status=success, started 2026-09-18T14:29:12Z, duration 135s
Run 7087 (deploy-itchbox.yml, same head) — status=success, started 2026-09-18T14:31:27Z, duration 204s
Earlier dispatch resumption at run 6781/6782 (head ebd1b7d 'ci: make itchbox deploy optional; skip gracefully when unreachable') on 2026-09-14T00:34:57Z
Subsequent commits (#62, #63, #64, #65, #66, #67, #68, plus #61) all built green through this morning

Runner state on blackhole:

/home/b/forgejo-runner-planish/data/.runner: id=35, no 'scope' key = user-level, label set includes 'ubuntu-latest:docker://node:20-bookworm', daemon Up 2 days
/home/b/forgejo-runner-mcp-directory/data/.runner: id=41, no 'scope' key = user-level, same labels, Up 57 minutes

Both daemons are running and dispatching chainbound jobs. The systemic condition referenced (Mark/planish#16, Mark/transcriber#136, Mark/nodedesk#55, Mark/kimi_agent_kin_app_sync#160) appears to have been addressed — those issues should be re-verified separately, but the chainbound-specific symptom is no longer present.

If CI breaks again on this repo, file a fresh issue. Closing this one retroactively per the §7 stale-closure pattern in the forgejo skill — fix landed organically, no further action needed here.

Closing as stale — the underlying runner-coverage condition has been resolved organically and CI is currently dispatching on Mark/chainbound. Evidence (live API check 2026-09-18): - Run 7086 (ci.yml, head 7cf0505 'fix #61') — status=success, started 2026-09-18T14:29:12Z, duration 135s - Run 7087 (deploy-itchbox.yml, same head) — status=success, started 2026-09-18T14:31:27Z, duration 204s - Earlier dispatch resumption at run 6781/6782 (head ebd1b7d 'ci: make itchbox deploy optional; skip gracefully when unreachable') on 2026-09-14T00:34:57Z - Subsequent commits (#62, #63, #64, #65, #66, #67, #68, plus #61) all built green through this morning Runner state on blackhole: - /home/b/forgejo-runner-planish/data/.runner: id=35, no 'scope' key = user-level, label set includes 'ubuntu-latest:docker://node:20-bookworm', daemon Up 2 days - /home/b/forgejo-runner-mcp-directory/data/.runner: id=41, no 'scope' key = user-level, same labels, Up 57 minutes Both daemons are running and dispatching chainbound jobs. The systemic condition referenced (Mark/planish#16, Mark/transcriber#136, Mark/nodedesk#55, Mark/kimi_agent_kin_app_sync#160) appears to have been addressed — those issues should be re-verified separately, but the chainbound-specific symptom is no longer present. If CI breaks again on this repo, file a fresh issue. Closing this one retroactively per the §7 stale-closure pattern in the forgejo skill — fix landed organically, no further action needed here.

Mark closed this issue

2026-09-18 15:38:17 +00:00