You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(cli): exclude server-side scheduling delay from the per-check timeout [RED-814]
Per-check timers (default 600s) all started at run start, so on large
staggered sessions — where the backend spreads non-priority checks
across up to 900s of SQS delay — the tail was reported as timed out
before those checks ever started. Timers now carry scheduling-delay
headroom (timeout + 900s, with a distinct did-not-start message) until
the check's run-start message arrives, then re-arm to the plain
timeout: --timeout measures execution, not queue delay.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HFcrNm7uzzkD1p87Nf9AhP
Copy file name to clipboardExpand all lines: packages/cli/src/commands/test.ts
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ export default class Test extends AuthCommand {
75
75
}),
76
76
'timeout': Flags.integer({
77
77
default: DEFAULT_CHECK_RUN_TIMEOUT_SECONDS,
78
-
description: 'A timeout (in seconds) to wait for checks to complete.',
78
+
description: 'A timeout (in seconds) to wait for each check result once the check starts running. Checks awaiting scheduling get additional headroom for the server-side dispatch stagger.',
description: 'A timeout (in seconds) to wait for checks to complete.',
65
+
description: 'A timeout (in seconds) to wait for each check result once the check starts running. Checks awaiting scheduling get additional headroom for the server-side dispatch stagger.',
0 commit comments