Skip to content

Commit 657d4b0

Browse files
committed
fix(soak): give the first diagnostics snapshot a 30s window
Both Windows runner soak legs died right after 'server running' while the daemon's own log shows a healthy diagnostics.start with valid paths — the wait polled 10s for a snapshot whose first WRITE lands one 5s interval after start and can exceed 10s on a cold 4-vCPU runner mid-initial-index (the VM's 18 cores never miss it; the x64 leg's SIGPIPE was the same failure path dying inside the pipeline). Budget doctrine: the wait sits above the worst case. Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>
1 parent 0c0111e commit 657d4b0

1 file changed

Lines changed: 7 additions & 1 deletion

File tree

‎scripts/soak-test.sh‎

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -559,7 +559,13 @@ wait_for_daemon_stop() {
559559
wait_for_diagnostics_snapshot() {
560560
local after_count="${1:-0}"
561561
local previous_path="${2:-}"
562-
local attempts=100
562+
# 30s, not a 10s sprint: the first snapshot lands one diagnostics interval
563+
# (5s) after start, and a cold 4-vCPU hosted runner mid-initial-index can
564+
# push the first WRITE past 10s (observed: both Windows runner soak legs
565+
# died right after 'server running' while the daemon's own log shows a
566+
# perfectly healthy diagnostics.start — the VM's 18 cores never miss the
567+
# window). Budget doctrine: the wait sits above the worst case.
568+
local attempts=300
563569
while [ "$attempts" -gt 0 ]; do
564570
local current_count
565571
current_count=$(diagnostics_start_count)

0 commit comments

Comments
 (0)