Reproduce the director broker exit after a Docker name-conflict 125 #1385

Merged
coilyco-ops merged 1 commit from issue-1244 into main 2026-07-15 10:34:21 +00:00
Owner

This adds a synthetic regression for the brokered Docker name-conflict 125 path and keeps the host dispatch broker alive after the failure. The test now matches the incident shape more closely by exercising exit status 125 explicitly, so we can prove the broker/request lifetime behavior without a live host repro.

  • Added a panic/classification check for the exit-125 name-conflict shape.
  • Updated the broker-survival regression to use the same failure shape and assert the failure classification.
  • Verified with go test ./....

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

This adds a synthetic regression for the brokered Docker name-conflict 125 path and keeps the host dispatch broker alive after the failure. The test now matches the incident shape more closely by exercising `exit status 125` explicitly, so we can prove the broker/request lifetime behavior without a live host repro. - Added a panic/classification check for the exit-125 name-conflict shape. - Updated the broker-survival regression to use the same failure shape and assert the failure classification. - Verified with `go test ./...`. closes #1244 ward.workflow: pull-request-and-merge
Test exit-125 broker name conflicts
All checks were successful
test / test (pull_request) Successful in 1m37s
0eae2ec267
Commenting is not possible because the repository is archived.
No reviewers
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!1385
No description provided.