coilyco-flight-deck/ward

Archived

Watch

Recover PR #1457 from stale running Actions state after context canceled #1462

Closed

opened 2026-07-15 14:01:36 +00:00 by coilyco-ops · 3 comments

coilyco-ops commented

2026-07-15 14:01:36 +00:00

Owner

Problem

PR #1457 for #1082 is blocked by a Forgejo Actions state drift: the raw job log shows the test job failed almost immediately after go test ./... started, but the Forgejo run UI and combined PR status still report the job as running/pending.

Evidence from QA/ops on 2026-07-15:

run 8619 (#2306) running test.yml pull_request #1457 "Remove hardcoded Forgejo KDL aliases"
ward agent pr status coilyco-flight-deck/ward#1457
combined status: pending
  test / test (pull_request) = pending

Raw log from /actions/runs/2306/jobs/0/attempt/1/logs shows:

2026-07-15T13:49:27Z go test ./...
2026-07-15T13:49:38Z [runner]: context canceled
... archive?path=/var/run/act/workflow/SUMMARY.md: context canceled
... archive?path=/var/run/act/workflow/pathcmd.txt: context canceled
2026-07-15T13:49:38Z Job failed

The run page still showed the job as running more than 11 minutes later, with go test marked running and lint waiting. That leaves #1457 neither mergeable by evidence nor cleanly repairable by the active engineer.

Acceptance

Recover PR #1457 from the stale Actions state using supported ward-native tools: rerun, close/reopen, or otherwise force a fresh test run for head b89cae4469ad4c036f6f22ec49ee522155594389 or a newer explicit head.
If rerun is impossible while Forgejo thinks the job is running, leave exact evidence and use the supported PR recovery path.
Do not merge #1457 until a fresh combined status is success for the current head.
Leave final evidence of the recovered green test run, or the exact remaining Forgejo runner/state blocker.

Related: #1082, #1457, run 8619 / #2306.

## Problem PR #1457 for #1082 is blocked by a Forgejo Actions state drift: the raw job log shows the test job failed almost immediately after `go test ./...` started, but the Forgejo run UI and combined PR status still report the job as running/pending. Evidence from QA/ops on 2026-07-15: ```text run 8619 (#2306) running test.yml pull_request #1457 "Remove hardcoded Forgejo KDL aliases" ward agent pr status coilyco-flight-deck/ward#1457 combined status: pending test / test (pull_request) = pending ``` Raw log from `/actions/runs/2306/jobs/0/attempt/1/logs` shows: ```text 2026-07-15T13:49:27Z go test ./... 2026-07-15T13:49:38Z [runner]: context canceled ... archive?path=/var/run/act/workflow/SUMMARY.md: context canceled ... archive?path=/var/run/act/workflow/pathcmd.txt: context canceled 2026-07-15T13:49:38Z Job failed ``` The run page still showed the job as `running` more than 11 minutes later, with `go test` marked running and lint waiting. That leaves #1457 neither mergeable by evidence nor cleanly repairable by the active engineer. ## Acceptance - Recover PR #1457 from the stale Actions state using supported ward-native tools: rerun, close/reopen, or otherwise force a fresh test run for head `b89cae4469ad4c036f6f22ec49ee522155594389` or a newer explicit head. - If rerun is impossible while Forgejo thinks the job is running, leave exact evidence and use the supported PR recovery path. - Do not merge #1457 until a fresh combined status is success for the current head. - Leave final evidence of the recovered green test run, or the exact remaining Forgejo runner/state blocker. Related: #1082, #1457, run 8619 / #2306.

coilyco-ops added the

autonomy

headless

priority

labels

2026-07-15 14:01:36 +00:00

coilyco-ops commented

2026-07-15 14:02:19 +00:00

Author

Owner

DISPATCH-DEFERRED: QA/ops filed this recovery but the Ward repo engineer pool is at capacity.

Evidence:

warded coilyco-flight-deck/ward#1462 --harness codex
ward: dispatch broker: ward agent engineer --harness codex: repo engineer limit is reached for coilyco-flight-deck/ward: 3 active engineer(s) (limit 3); pass --override-capacity to exceed real running capacity (dispatch log: /Users/kai/.ward/agent-logs/dispatch/20260715T140143Z-director-codex-jp85-coilyco-flight-deck-ward-1462.log)

This issue remains ready for sibling dispatch as soon as capacity opens.

DISPATCH-DEFERRED: QA/ops filed this recovery but the Ward repo engineer pool is at capacity. Evidence: ```text warded coilyco-flight-deck/ward#1462 --harness codex ward: dispatch broker: ward agent engineer --harness codex: repo engineer limit is reached for coilyco-flight-deck/ward: 3 active engineer(s) (limit 3); pass --override-capacity to exceed real running capacity (dispatch log: /Users/kai/.ward/agent-logs/dispatch/20260715T140143Z-director-codex-jp85-coilyco-flight-deck-ward-1462.log) ``` This issue remains ready for sibling dispatch as soon as capacity opens.

coilyco-ops referenced this issue from a commit

2026-07-29 16:40:43 +00:00

chore: record PR 1457 Actions recovery

coilyco-ops closed this issue

2026-07-29 16:40:43 +00:00

coilyco-ops commented

2026-07-29 16:46:51 +00:00

Author

Owner

WARD-WORKFLOW: done ✅

details

Recovered: PR #1457 head 066cd6565c41c86b118f8c78a9a4578b3aa1bb86 passed fresh Actions run 8633 (display #2313) in 49s and merged as 0f446a0d66f565b8ce8a76526f760adbe290744d.

Landed: recovery record 02bbe3ad; main merge 8cc572d3; promote 13334 and release 13335 green.

workflow: merge-remote-main; review summary: in-container review gate intentionally skipped because implementation and QA are role-separated; QA is a separate, opt-in exact-commit verification role bound to the exact candidate commit.

Felt: pleasantly anticlimactic—the delayed dispatch found the native recovery already complete, leaving evidence and closure.

Confidence: high.

Surprises: aosguard lacked its host AWS identity; Ward and public Forgejo evidence were sufficient.

Follow-ups: refresh the root-owned host Ward binary from verified v0.860.0; none for PR #1457.

— Codex

WARD-WORKFLOW: done ✅ <details><summary>details</summary> Recovered: PR #1457 head `066cd6565c41c86b118f8c78a9a4578b3aa1bb86` passed fresh Actions run `8633` (display `#2313`) in 49s and merged as `0f446a0d66f565b8ce8a76526f760adbe290744d`. Landed: recovery record `02bbe3ad`; main merge `8cc572d3`; promote `13334` and release `13335` green. workflow: merge-remote-main; review summary: in-container review gate intentionally skipped because implementation and QA are role-separated; QA is a separate, opt-in exact-commit verification role bound to the exact candidate commit. Felt: pleasantly anticlimactic—the delayed dispatch found the native recovery already complete, leaving evidence and closure. Confidence: high. Surprises: `aosguard` lacked its host AWS identity; Ward and public Forgejo evidence were sufficient. Follow-ups: refresh the root-owned host Ward binary from verified `v0.860.0`; none for PR #1457. — Codex </details>

coilyco-ops commented

2026-07-29 16:47:05 +00:00

Author

Owner

WARD-WORKFLOW: reservation-released

release details

Run finished with WARD-WORKFLOW: done ✅.

ward container reap released container engineer-codex-ward-1462 (--harness codex): the terminal outcome supersedes the reservation, so a later redispatch no longer needs --override-reservation.

— Codex, via ward agent

WARD-WORKFLOW: reservation-released <details><summary>release details</summary> Run finished with `WARD-WORKFLOW: done ✅`. `ward container reap` released container `engineer-codex-ward-1462` (`--harness codex`): the terminal outcome supersedes the reservation, so a later redispatch no longer needs `--override-reservation`. </details>  — Codex, via `ward agent`

Commenting is not possible because the repository is archived.

No milestone

No project

No assignees

1 participant

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/ward#1462

No description provided.

Rows
Columns