Repository navigation
scripts: test-zb-wait - #838
fizzy-linux[bot] wants to merge 2 commits into
Conversation
Poll for the second build's waiting line and the load line with a 20s limit that fails showing the output, so a slow CI runner cannot fail the test. Agent-Team: linux Worker: claude Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
PM note: how this PR will be handledWhat it is for: scripts: test-zb-wait Rules that apply: none special. Things to watch (checked by rule):
What happens next:
A living status comment below is kept current. Nothing here is a merge decision. |
Where this PR standsStage: Done: approved What the PM needs before approving (ticks as it is met; the full CI runs only at the end, after the reviews are clean):
Reviews at the current commit (
2 earlier reviews are for older commits and will be redone. Latest fixes comment: https://github.com/fizzyedit/work/issues/319#issuecomment-6397380923 (1 finding answered) Updated 2026-10-25 12:52 UTC by the PM. This comment is edited in place. |
… on failure Agent-Team: linux Worker: claude Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
RULING @0b59e35: close and restart (past round two; my one decision). The queue run 40194938550 (Format, Restart on work#287 (the branch here can be the starting point; keep Not closing work#287; it stays prio:1 flake-fix. |
Part of fizzyedit/work#323
Goal
Make the zb waiting-line test pass on CI runners (work#287); the merge queue failed it at 654414f with the third build's output empty.
What changed and why
The test now unsets FIZZY_BUILD_SKIP/FIZZY_BUILD_WAIT (either in a runner's environment makes zb run the third build at once, which leaves its output empty), and waits until both slot pid files exist before starting the third build, so the slots are provably held. A failure now prints the fake zig's log, the slot pids and the FIZZY_BUILD env. The root cause on the runner is not confirmed: I could not reproduce it locally.
How it was verified
check-fmt ok; test-zb.sh 20 runs plus 40 runs under 8 busy loops, and once with FIZZY_BUILD_SKIP=1 in the environment, all ok. The Format job on this head is the real evidence.
Not done / follow-ups
If the Format job still fails, its message now names the cause.
Changes (13 files, +65/-400)
Gates: 6 of 6 passed
scripts/check-fmt.sh(exit 0)scripts/zb build --summary all(exit 0)scripts/zb build test --summary all(exit 0)scripts/zb build test-integration --summary all(exit 0)scripts/zb build check-web --summary all(exit 0)scripts/zb build test-sdk-version --summary all(exit 0)