coilyco-flight-deck/ward
2
0
Fork 0
Code Issues 107 Pull requests 1 Projects Releases 737 Packages Wiki Activity Actions 1

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
Conversation 0 Commits 1 Files changed 1 +15 -6
coilyco-ops commented 2026-07-15 10:32:00 +00:00
Member
Copy link

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
Details
0eae2ec267
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
pressure-test
Cold-read release pressure-test findings and coordination

  
sunday-sprint
Burn-down by Sunday 2026-06-07

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
pressure-test
sunday-sprint
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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!1385
No description provided.