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
{{ message }}
Repository navigation
chore: local stop-test-gate hook timeout (exit=143) #123
The local stop-test-gate.sh hook consistently exits with code 143 (SIGTERM) when running the full test suite via turbo test. All tests pass but the process is killed before completion due to the hook's timeout.
Behavior
Hook detects 52+ source files → triggers full suite fallback
turbo test runs all packages (opencode + app + console-app)
Tests pass individually but the full suite exceeds the hook's timeout
Process receives SIGTERM → exit code 143 (128 + 15)
Fix Options
Increase the hook timeout for turbo test execution
Run only the affected package's tests instead of full suite
Use --filter to scope turbo test to changed packages
Add special handling for exit code 143 (distinguish timeout from real failure)
Impact
Non-blocking for development — all tests pass
Noise in development workflow
Ref
Observed consistently across all sessions since hook deployment
Related to #129. The stop-test-gate hook timeout (exit=143) is caused by turbo test full suite exceeding the hook's timeout on slower runners. This is a local development issue, not CI-blocking.
Workaround: Use --filter to scope turbo test to changed packages. Proper fix: Tracked in #129 (runner performance).
Turbo --filter: Added Phase 1.5 that extracts changed package names from SOURCE_FILES/TEST_FILES and scopes turbo test --filter=<pkg> instead of running full suite
Monorepo timeout: Increased from 60s to 120s when monorepo detected
Cross-cutting threshold: Dynamically raised from 20→40 for monorepos
Root cause: timeout 60 sends SIGTERM → exit 143, which was not recognized as timeout. Script fell through to exit 2 (block session).
Activity
terisuke commentedon Apr 6, 2026
Related to #129. The stop-test-gate hook timeout (exit=143) is caused by
turbo testfull suite exceeding the hook's timeout on slower runners. This is a local development issue, not CI-blocking.Workaround: Use
--filterto scope turbo test to changed packages.Proper fix: Tracked in #129 (runner performance).
terisuke commentedon Apr 6, 2026
Fixed locally in ~/.claude/hooks/stop-test-gate.sh. Changes:
turbo test --filter=<pkg>instead of running full suiteRoot cause:
timeout 60sends SIGTERM → exit 143, which was not recognized as timeout. Script fell through toexit 2(block session).