coilyco-flight-deck/ward

Watch

Inspect gate-and-promote failure after Ward launch-path repair #1471

New issue

Closed

opened 2026-07-16 07:48:25 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-16 07:48:25 +00:00

Member

Follow-up to #1468 and commit a95acbcc.

Forgejo gate-and-promote run 2322 failed for a95acbcc after 1m59s:
https://forgejo.coilysiren.me/coilyco-flight-deck/ward/actions/runs/2322/jobs/0

Local evidence is green:

ward exec build
ward exec vet
ward exec lint
ward exec test with an isolated HOME and the existing module cache
pre-commit run --all-files

The purpose-built Actions log read returned 404 for run 2322, job 0, attempt 1, so this sealed run cannot determine whether the failure is runner state, a transient, or a code failure.

A director or ops run needs to inspect the live job log, classify the failure, and verify promotion. If the log proves a repository defect, land one locally grounded fix. Do not probe CI with speculative pushes.

Follow-up to #1468 and commit a95acbcc. Forgejo gate-and-promote run 2322 failed for a95acbcc after 1m59s: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/actions/runs/2322/jobs/0 Local evidence is green: * ward exec build * ward exec vet * ward exec lint * ward exec test with an isolated HOME and the existing module cache * pre-commit run --all-files The purpose-built Actions log read returned 404 for run 2322, job 0, attempt 1, so this sealed run cannot determine whether the failure is runner state, a transient, or a code failure. A director or ops run needs to inspect the live job log, classify the failure, and verify promotion. If the log proves a repository defect, land one locally grounded fix. Do not probe CI with speculative pushes.

coilyco-ops added the

autonomy

live-collab

label

2026-07-16 07:48:25 +00:00

coilyco-ops commented

2026-07-18 06:12:11 +00:00

Author

Member

Follow-up live evidence after ward#1480 and ward#1472 landed. Promote run 2323 failed for be9c675fea: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/actions/runs/2323. Local evidence is green: ward exec build, focused container and release-contract tests, and the complete existing pre-commit suite. The supported actions-log read for run 2323, job 0, attempt 1 returns 404, so this run cannot classify the live failure. A director or ops run needs to inspect the Forgejo UI log and verify promotion. No speculative CI retry or follow-up code push was made.

Follow-up live evidence after ward#1480 and ward#1472 landed. Promote run 2323 failed for be9c675fea147626d464655207eeab5d5df245ea: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/actions/runs/2323. Local evidence is green: ward exec build, focused container and release-contract tests, and the complete existing pre-commit suite. The supported actions-log read for run 2323, job 0, attempt 1 returns 404, so this run cannot classify the live failure. A director or ops run needs to inspect the Forgejo UI log and verify promotion. No speculative CI retry or follow-up code push was made.

coilyco-ops added the

priority

label

2026-07-29 03:47:14 +00:00

coilyco-ops added

priority

and removed

priority

labels

2026-07-29 06:27:14 +00:00

coilyco-ops commented

2026-07-31 08:12:40 +00:00

Author

Member

Closing this point-in-time CI incident as historical evidence rather than durable backlog work. The remaining concrete release-pipeline migration is #1492.

coilyco-ops closed this issue

2026-07-31 08:12:42 +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/ward#1471

No description provided.

Rows
Columns