Investigate one-second Forgejo Actions failures on main #602

New issue

Closed

opened 2026-07-23 10:41:23 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-23 10:41:23 +00:00

Owner

Live evidence

Commit 73795ab passed ward exec test and ward exec pre-commit locally, then both Forgejo push workflows failed almost immediately:

Both started around 10:39:53Z and ended as failures within one second. The preceding main commit also has failed runs 1460 and 1461, while the earlier main runs 1458 and 1459 succeeded. The Actions log fetch route returned 404 for the attempted run/job identifiers, so this sealed engineer session cannot establish whether the failure is runner scheduling, workflow bootstrap, or another live Actions condition.

Interactive verification

An operator or director with the Forgejo Actions UI and runner visibility should inspect the raw failure text for runs 1462 and 1463, confirm runner availability and workflow startup, then decide whether the fix belongs in workflow config or live runner operations. Do not probe the pipeline with speculative code pushes.

Local evidence

The repository worktree is clean at 73795ab. ward exec test and the full offline pre-commit suite, including trufflehog, passed before push.

## Live evidence Commit `73795ab` passed `ward exec test` and `ward exec pre-commit` locally, then both Forgejo push workflows failed almost immediately: * lint: https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/actions/runs/1462 * secret scan: https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/actions/runs/1463 Both started around 10:39:53Z and ended as failures within one second. The preceding main commit also has failed runs 1460 and 1461, while the earlier main runs 1458 and 1459 succeeded. The Actions log fetch route returned 404 for the attempted run/job identifiers, so this sealed engineer session cannot establish whether the failure is runner scheduling, workflow bootstrap, or another live Actions condition. ## Interactive verification An operator or director with the Forgejo Actions UI and runner visibility should inspect the raw failure text for runs 1462 and 1463, confirm runner availability and workflow startup, then decide whether the fix belongs in workflow config or live runner operations. Do not probe the pipeline with speculative code pushes. ## Local evidence The repository worktree is clean at `73795ab`. `ward exec test` and the full offline pre-commit suite, including trufflehog, passed before push.

coilyco-ops added the

autonomy

live-collab

label

2026-07-23 10:41:32 +00:00

coilyco-ops commented

2026-07-23 18:11:16 +00:00

Author

Owner

Commit b51f639 reproduces the same live-only pattern after passing ward exec pre-commit and ward exec test locally:\n\n* lint: https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/actions/runs/1470\n* secret scan: https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/actions/runs/1471\n\nBoth runs stopped as failures within one second. The agent made no follow-up probe push.

Commit b51f639 reproduces the same live-only pattern after passing ward exec pre-commit and ward exec test locally:\n\n* lint: https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/actions/runs/1470\n* secret scan: https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/actions/runs/1471\n\nBoth runs stopped as failures within one second. The agent made no follow-up probe push.

coilyco-ops commented

2026-07-27 03:14:19 +00:00

Author

Owner

New occurrence from ward PR #1525 on 2026-07-26:

Run: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/actions/runs/2448
Head: 7343aeecb87e1fdd5b1174c171e72c50b461ce7b
The run waited about 6m43s for a runner, executed for 64s, then reported failure.
Forgejo identifies internal run id 11904 and Actions task id 18568.
The guarded log endpoint returns 404 for run identifiers 2448 and 11904 with both the exposed job id 0 and task id 18568 at attempt 1.
The Actions page could not be inspected because no authenticated browser surface is available in this session.

Local evidence is green: focused authenticated and rejected private-LFS tests, build, vet, lint, and the full pre-commit suite including trufflehog all passed after merging current main.

Operator action: inspect the raw failure text for run 2448 in the Forgejo Actions UI, return the failing step and log, and determine why the API continues to expose jobs/0 while every concrete log request returns 404. The agent made one grounded push and did not rerun or probe CI with further commits.

New occurrence from ward PR #1525 on 2026-07-26: * Run: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/actions/runs/2448 * Head: 7343aeecb87e1fdd5b1174c171e72c50b461ce7b * The run waited about 6m43s for a runner, executed for 64s, then reported failure. * Forgejo identifies internal run id 11904 and Actions task id 18568. * The guarded log endpoint returns 404 for run identifiers 2448 and 11904 with both the exposed job id 0 and task id 18568 at attempt 1. * The Actions page could not be inspected because no authenticated browser surface is available in this session. Local evidence is green: focused authenticated and rejected private-LFS tests, build, vet, lint, and the full pre-commit suite including trufflehog all passed after merging current main. Operator action: inspect the raw failure text for run 2448 in the Forgejo Actions UI, return the failing step and log, and determine why the API continues to expose jobs/0 while every concrete log request returns 404. The agent made one grounded push and did not rerun or probe CI with further commits.

coilyco-ops referenced this issue from coilyco-flight-deck/ward

2026-07-27 03:14:34 +00:00

Authenticate Forgejo Git LFS during private-repo engineer preclone #1524

coilyco-ops referenced this issue from coilyco-flight-deck/ward

2026-07-28 02:47:41 +00:00

Authenticate Forgejo Git LFS during private-repo engineer preclone #1524

coilyco-ops referenced this issue from coilyco-flight-deck/ward

2026-07-28 03:47:33 +00:00

Authenticate Forgejo Git LFS preclone #1525

coilyco-ops

2026-07-29 03:46:25 +00:00