[GH-ISSUE #149] processCapture integration tests timeout under default Vitest limits #95

New issue

Closed

opened 2026-10-15 18:21:05 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:21:05 +00:00

Owner

Originally created by @morluto on GitHub (Jul 14, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/149

Running npm test fails intermittently on two process-capture integration tests with default Vitest timeout.

Observed in local run:

tests/processCapture.test.ts:708 renders terminal state, records shim invocations, and captures literal checkpoints
tests/processCapture.test.ts:936 samples and cleans a source-owned child and grandchild process tree

Both tests report:

Test timed out in 5000ms.
With retries configured (retry: 2) in vitest.config.ts, each failed test retries and still times out.

Impact:

Full suite cannot complete reliably.

Suggested fix:

Set explicit per-test timeout on these two cases (e.g. 20_000 ms).
Consider a more deterministic fixture completion condition than string-matching checkpoint latency.

Originally created by @morluto on GitHub (Jul 14, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/149 Running `npm test` fails intermittently on two process-capture integration tests with default Vitest timeout. Observed in local run: - tests/processCapture.test.ts:708 `renders terminal state, records shim invocations, and captures literal checkpoints` - tests/processCapture.test.ts:936 `samples and cleans a source-owned child and grandchild process tree` Both tests report: - `Test timed out in 5000ms.` - With retries configured (`retry: 2`) in `vitest.config.ts`, each failed test retries and still times out. Impact: - Full suite cannot complete reliably. Suggested fix: - Set explicit per-test timeout on these two cases (e.g. 20_000 ms). - Consider a more deterministic fixture completion condition than string-matching checkpoint latency.

bsakaguchi

2026-10-15 18:21:05 +00:00