Retry timed-out release run for context-level removal #217

New issue

Closed

opened 2026-08-06 05:16:26 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-06 05:16:26 +00:00

Member

Evidence

Canonical main is a5e80c2d86bccf51b6185b5633966659c99ad498.
Forgejo release run #166 (API run 15731) started at 2026-08-06T04:44:29Z and stopped at 2026-08-06T05:14:30Z.
Forgejo reports status: cancelled after 1801s, matching the workflow's 30-minute job timeout.
The same revision passes ward exec test locally, including Go, evaluation-result, scorecard, palette, and complete pre-commit validation.
Issue #215 closed from the landed commits.
The newest published release remains v2.11.0. No release or package-manager update was created for this revision.
The Forgejo API run-log and run-job endpoints returned 404, so the blocking step is visible only through the Actions UI or runner-side evidence.

Operator action

Inspect run #166 in the Forgejo Actions UI or runner logs and identify the step that consumed the timeout.
If the timeout is runner or Actions state rather than a repository defect, retry release.yml for current main without changing the commit.
If the log exposes a repository defect, return the failing step and relevant log excerpt to Engineering before any new push.

Required evidence

A terminal successful release run for a5e80c2d86bccf51b6185b5633966659c99ad498.
The published release and complete attached artifact set.
Homebrew formula and Scoop manifest updates for the published tag, or an explicit skipped-secret warning from the successful run.

## Evidence * Canonical `main` is `a5e80c2d86bccf51b6185b5633966659c99ad498`. * Forgejo release run [#166](https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/actions/runs/166) (API run `15731`) started at `2026-08-06T04:44:29Z` and stopped at `2026-08-06T05:14:30Z`. * Forgejo reports `status: cancelled` after `1801s`, matching the workflow's 30-minute job timeout. * The same revision passes `ward exec test` locally, including Go, evaluation-result, scorecard, palette, and complete pre-commit validation. * Issue #215 closed from the landed commits. * The newest published release remains v2.11.0. No release or package-manager update was created for this revision. * The Forgejo API run-log and run-job endpoints returned 404, so the blocking step is visible only through the Actions UI or runner-side evidence. ## Operator action 1. Inspect run #166 in the Forgejo Actions UI or runner logs and identify the step that consumed the timeout. 2. If the timeout is runner or Actions state rather than a repository defect, retry `release.yml` for current `main` without changing the commit. 3. If the log exposes a repository defect, return the failing step and relevant log excerpt to Engineering before any new push. ## Required evidence * A terminal successful release run for `a5e80c2d86bccf51b6185b5633966659c99ad498`. * The published release and complete attached artifact set. * Homebrew formula and Scoop manifest updates for the published tag, or an explicit skipped-secret warning from the successful run.

coilyco-ops added the

autonomy

live-collab

label

2026-08-06 05:16:30 +00:00

coilyco-ops commented

2026-08-06 05:41:55 +00:00

Author

Member

Resolved

Before-state: release run #166 for a5e80c2d86bccf51b6185b5633966659c99ad498 timed out after 30m1s.
Cause evidence: repository validation reached pre-commit environment installation, then the runner ended with context deadline exceeded while reading Docker container files. Earlier Go, packaging, palette, and contract checks had passed.
Mutation: dispatched release.yml once against unchanged main.
After-state: release run #167 completed successfully on the same commit in 1m57s. Validation completed in 1m13s.
Publication: v2.12.0 is published with all seven expected artifacts.
Homebrew: formula update landed at d0e253d.
Scoop: manifest update landed at 2e37829.
Rollback status: no rollback required. No additional retry is pending.
Follow-up owner: none. The required release and package-manager evidence is complete.

## Resolved * Before-state: release run [#166](https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/actions/runs/166) for `a5e80c2d86bccf51b6185b5633966659c99ad498` timed out after 30m1s. * Cause evidence: repository validation reached pre-commit environment installation, then the runner ended with `context deadline exceeded` while reading Docker container files. Earlier Go, packaging, palette, and contract checks had passed. * Mutation: dispatched `release.yml` once against unchanged `main`. * After-state: release run [#167](https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/actions/runs/167) completed successfully on the same commit in 1m57s. Validation completed in 1m13s. * Publication: [v2.12.0](https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/releases/tag/v2.12.0) is published with all seven expected artifacts. * Homebrew: formula update landed at [d0e253d](https://forgejo.coilysiren.me/coilyco-flight-deck/homebrew-tap/commit/d0e253d7f5f813d118f84bee3a1100877503241e). * Scoop: manifest update landed at [2e37829](https://forgejo.coilysiren.me/coilyco-flight-deck/scoop-bucket/commit/2e3782954db27b713f04f8b14157a142830b52ae). * Rollback status: no rollback required. No additional retry is pending. * Follow-up owner: none. The required release and package-manager evidence is complete.

coilyco-ops closed this issue

2026-08-06 05:42:00 +00:00

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/agent-compose#217

No description provided.

Rows
Columns