main has been red since 2026-08-17: TestClassifyForgejoPRRepairBuckets, promote and release stalled #1681

Closed

opened 2026-08-24 01:23:54 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-24 01:23:54 +00:00

Owner

main fails its own gate and has since 2026-08-17. Nothing has promoted or released in a week.

The failure

promote.yml run 22299, job 36616, 2026-08-17T20:45:12Z:

    --- FAIL: TestClassifyForgejoPRRepairBuckets/main_red (0.00s)
    --- FAIL: TestClassifyForgejoPRRepairBuckets/merge_queue_churn (0.00s)
    --- FAIL: TestClassifyForgejoPRRepairBuckets/pr_regression (0.00s)
FAIL	github.com/coilyco-flight-deck/ward/cmd/ward	27.625s

Three subtests of one Go test in cmd/ward. test.yml run 25880 on PR #1680 fails identically today, so this is standing breakage rather than a flaky run.

What it blocks

promote.yml re-runs the full gate on every push to main and only fast-forwards release when green, so release has not advanced since 2026-08-17 and release.yml has cut nothing. That matches the tap, which still pins ward at 0.887.0.

Every pull request inherits the red, so no PR can go green on its own merits. #1680 is a one-line README addition and its CI fails on exactly these three subtests. I am leaving it open and unmerged rather than merging a red PR.

There is a grim joke in a test named main_red being the thing that is red.

Also failing locally, separately

pre-commit run --all-files on clean main fails two more hooks that are not in promote's gate:

FAIL: cmd/ward/agent.go:1338: comment block of 3 lines starting at 1336.
FAIL: cmd/ward/agent_flags_test.go:38: comment block of 3 lines starting at 36.
FAIL: cmd/ward/agent.go:1338: dead source doc reference docs/ward-agent-dispatch.md

The dead reference is real. docs/ward-agent-dispatch.md does not exist, and no doc in docs/ mentions autonomy at all, so the autonomy-ceiling contract that comment points at is undocumented rather than moved. I did not repoint it, because there is no correct target to point at and I would have been guessing about a security gate.

Ask

Fix the test, or if the behavior changed deliberately and the fixtures did not, update them. Once main is green, #1680 merges on its own.

Raised by devrel during a cross-repo README pass. Go tests are outside a content change, so handing over. Parent audit: coilysiren/inbox#397.

`main` fails its own gate and has since **2026-08-17**. Nothing has promoted or released in a week. ## The failure `promote.yml` run 22299, job 36616, 2026-08-17T20:45:12Z: ``` --- FAIL: TestClassifyForgejoPRRepairBuckets/main_red (0.00s) --- FAIL: TestClassifyForgejoPRRepairBuckets/merge_queue_churn (0.00s) --- FAIL: TestClassifyForgejoPRRepairBuckets/pr_regression (0.00s) FAIL github.com/coilyco-flight-deck/ward/cmd/ward 27.625s ``` Three subtests of one Go test in `cmd/ward`. `test.yml` run 25880 on PR #1680 fails identically today, so this is standing breakage rather than a flaky run. ## What it blocks `promote.yml` re-runs the full gate on every push to `main` and only fast-forwards `release` when green, so `release` has not advanced since 2026-08-17 and `release.yml` has cut nothing. That matches the tap, which still pins `ward` at `0.887.0`. Every pull request inherits the red, so no PR can go green on its own merits. #1680 is a one-line README addition and its CI fails on exactly these three subtests. I am leaving it open and unmerged rather than merging a red PR. There is a grim joke in a test named `main_red` being the thing that is red. ## Also failing locally, separately `pre-commit run --all-files` on clean `main` fails two more hooks that are not in promote's gate: ``` FAIL: cmd/ward/agent.go:1338: comment block of 3 lines starting at 1336. FAIL: cmd/ward/agent_flags_test.go:38: comment block of 3 lines starting at 36. FAIL: cmd/ward/agent.go:1338: dead source doc reference docs/ward-agent-dispatch.md ``` The dead reference is real. `docs/ward-agent-dispatch.md` does not exist, and no doc in `docs/` mentions autonomy at all, so the autonomy-ceiling contract that comment points at is undocumented rather than moved. I did not repoint it, because there is no correct target to point at and I would have been guessing about a security gate. ## Ask Fix the test, or if the behavior changed deliberately and the fixtures did not, update them. Once `main` is green, #1680 merges on its own. Raised by devrel during a cross-repo README pass. Go tests are outside a content change, so handing over. Parent audit: `coilysiren/inbox#397`.

coilyco-ops added the

role/platform

priority

labels

2026-08-25 08:11:40 +00:00

coilyco-ops referenced this issue from a commit

2026-08-25 08:36:40 +00:00

fix(test): state the mirrored-verb set instead of reading this repo's ward.yaml

coilyco-ops referenced this issue from a pull request that will close it,

2026-08-25 08:36:59 +00:00

fix(test): state the mirrored-verb set instead of reading this repo's ward.yaml #1682

coilyco-ops closed this issue