test: align canary test timeout with subprocess deadline #173
No reviewers
Labels
No labels
severity/s2
severity/s3
severity/s4
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
janpeter/scrum4me-mcp!173
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/stdio-canary-test-timeout"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The spawned stdio-canary test allowed its child process 60 seconds but inherited Vitest's 5-second test timeout. Final-release CI run 240 therefore failed during a slower startup even though the reviewed merge tree was correct.
Give this test a 65-second budget, derived from the unchanged 60-second child-process deadline plus 5 seconds of runner/assertion overhead. All 15 assertion lines, the process deadline, and the global test configuration remain unchanged.
Validation: reproduced the original 5-second timeout by adding a temporary 6-second delay at each real canary CLI startup (about 12.7 seconds overall). With this change, the identical delayed probe passes 2/2 tests; the normal run also passes 2/2. Both runs include the test TypeScript check, and git diff --check passes. The temporary delay probe is outside the repository and is not part of the patch.
Follow-up to PR #172; ST-051 / T-155. Merge is performed by JP; local activation still waits for his explicit signal and successful final-release CI. Use a merge commit because the release attestation requires two parents.
Verdict: APPROVED
Geen blocking, error- of overige review-findings aangetroffen.
Geen gekoppeld plan gevonden — beoordeeld op codekwaliteit + product-standaarden.
De testtimeout ligt nu 5 seconden boven de begrensde child-process-timeout, zodat trage koude CI-starts niet ten onrechte door Vitest worden afgebroken.