feat(scriptb): Move the stress durations into config.ttl, and restore the timeout sooner

SSD_RUNTIME / SSD_COUNT and USB_RUNTIME / USB_COUNT replace the values that
were hard-coded in Script B, so a site changes them in one place. COUNT is
passed straight through as --passes.

--runtime is the job's OVERALL limit, not a per-pass one: qfx5252-stress-*
stops after RUNTIME seconds whatever --passes says. RUNTIME 600 is a ten
minute stress, not 600 x COUNT. A 24 hour soak needs RUNTIME 86400.

Also restore timeout = 0 on the cdc_ncm success path. It was restored only at
:skip_ping, which the success path reaches several waits later - until then
every wait gave up after 15 s instead of blocking, and a wait that returns
without eating the prompt puts the macro a beat ahead of the DUT.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014RetWKFZFG1ZHcitQAyhwM
This commit is contained in:
2026-09-04 22:44:05 +08:00
co-authored by Claude Opus 5
parent a9c56ee1d4
commit 0d2faef565
2 changed files with 14 additions and 2 deletions
+8
View File
@@ -17,6 +17,14 @@ FAN_SPEED = 100
SWB_UNIT0 = 1 ; 1 = this DUT has switch unit 0, wait for it ; 0 = skip
SWB_UNIT1 = 1 ; 1 = this DUT has switch unit 1, wait for it ; 0 = skip
;================================================================
; Stress_Test
;================================================================
SSD_RUNTIME = 600 ; Unit seconds, 600 = 10 minutes
SSD_COUNT = 720 ; Total time = SSD_RUNTIME * SSD_COUNT
USB_RUNTIME = 600 ; Unit seconds, 600 = 10 minutes
USB_COUNT = 720 ; Total time = USB_RUNTIME * USB_COUNT
;================================================================
; Prompt Definitions
;================================================================