spawn-test: bump timeout constants to avoid CI flakiness #12

Closed
opened 2026-07-02 01:05:57 -04:00 by the_og · 0 comments
Owner

Follow-up from PR #11 supervisor review (item 3).

The crashed/exited tests use 0.3–0.5 s timeouts, which can misfire on a slow CI runner where Python interpreter startup takes longer than expected (a subprocess that takes >300 ms to start would time out and be classified "ok" instead of "crashed"/"exited").

Fix: Bump the timeout argument in the non-"ok" spawn test cases from 0.3–0.5 s to 1–2 s. The "ok" (timeout) path can stay at 0.3 s since timing out means success there.

Relevant tests: test_spawn_test_crashed, test_spawn_test_exited_cleanly, test_spawn_test_stderr_captured in tests/test_core.py.

Follow-up from PR #11 supervisor review (item 3). The crashed/exited tests use 0.3–0.5 s timeouts, which can misfire on a slow CI runner where Python interpreter startup takes longer than expected (a subprocess that takes >300 ms to start would time out and be classified "ok" instead of "crashed"/"exited"). **Fix:** Bump the timeout argument in the non-"ok" spawn test cases from 0.3–0.5 s to 1–2 s. The "ok" (timeout) path can stay at 0.3 s since timing out _means_ success there. Relevant tests: `test_spawn_test_crashed`, `test_spawn_test_exited_cleanly`, `test_spawn_test_stderr_captured` in `tests/test_core.py`.
the_og added the P0 label 2026-07-02 01:05:57 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: the_og/better-claude-config#12