mosaicstack/stack
25
0
Fork 1
Code Issues 365 Pull Requests 13 Actions Packages Projects Releases 15 Wiki Activity

logs: Darkwing row 103 build.md, test-task ran without Docker (#1597)

Browse Source 
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
jason.woltje
2026-10-13 16:13:44 -05:00
co-authored by Claude Opus 5.5
parent 486c4aad34
commit d38a7a3b6b
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
agents/darkwing/work/queue-103/r1/build.md
+2
View File
@@ -136,4 +136,6 @@ test-task rc=0 21:11:07-21:11:09 selftest: 26 passed, 0 failed
ledger rc=0 ℹ pass 78 ℹ fail 0 ℹ skipped 0
```
test-task.sh ran with `DOCKER_HOST=unix:///nonexistent`, set by line 19 of `gate.sh` and carried over from my earlier gate scripts. Under that value `docker info` fails, so test-task.sh skipped its adapter-seam, workspace/capability, live-task and recall cases: 26 passed, where a run with a working Docker daemon gives 98. The daemon on this host was up (`docker info` exits 0 without the override), so this was the script's choice, not an outage. The row 103 code in cli, seat and harness doesn't reach those cases, and Sage's landing gate runs them with Docker. Nothing was rerun. Every other suite ran with DOCKER_HOST unset.
Before the gate, the race test's "no claim file left over" check listed the whole bus-host directory and failed on the host's own launch.sock, git.sock and sessions.json; it now lists only `host.*` names. The Docker network the gate created (wt_default) was removed after each run, and no process of mine was left.