docs: note transient promote failures #1329

Merged
coilyco-ops merged 1 commit from issue-1323 into main 2026-07-15 05:53:26 +00:00
Member

Run 8253 failed in go test after #1299 merged, but later promote runs on newer main pushes succeeded (8255, 8271, 8276). That makes this look transient/superseded rather than a regression in the PR-pressure redispatch change. I added a troubleshooting note so operators know to treat a later successful promote as the authoritative signal.

  • ward exec test passed locally.
  • The PR includes the required issue trailer and workflow marker.

closes #1323
ward.workflow: pull-request-and-merge

Run 8253 failed in `go test` after #1299 merged, but later promote runs on newer main pushes succeeded (8255, 8271, 8276). That makes this look transient/superseded rather than a regression in the PR-pressure redispatch change. I added a troubleshooting note so operators know to treat a later successful promote as the authoritative signal. - `ward exec test` passed locally. - The PR includes the required issue trailer and workflow marker. closes #1323 ward.workflow: pull-request-and-merge
docs: note transient promote failures
All checks were successful
test / test (pull_request) Successful in 1m1s
9b6c46c432
closes #1323
Sign in to join this conversation.
No description provided.