2ad9d23ad9
Some checks failed
CI / Unit & Component Tests (pull_request) Failing after 4m56s
CI / OCR Service Tests (pull_request) Successful in 46s
CI / Backend Unit Tests (pull_request) Failing after 16m17s
CI / fail2ban Regex (pull_request) Failing after 2m5s
CI / Semgrep Security Scan (pull_request) Successful in 43s
CI / Compose Bucket Idempotency (pull_request) Successful in 2m7s
SDD Gate / RTM Check (pull_request) Successful in 35s
SDD Gate / Contract Validate (pull_request) Successful in 49s
SDD Gate / Constitution Impact (pull_request) Successful in 32s
All 2327 tests pass, but the build went red: after the suite finishes, Surefire calls System.exit(0) and the single reused fork then closes ~32 cached Spring contexts at once — each tearing down a Testcontainers Postgres + HikariCP pool — which overruns Surefire's 30s default post-exit grace. Surefire force-kills the fork and reports a fork timeout (BUILD FAILURE with 0 failures). The session-cleanup InterruptedException and Testcontainers reaper NotFoundException in the log are symptoms of that contended teardown. Set the previously-unset forkedProcessExitTimeoutInSeconds to 120s. This is a different knob from forkedProcessTimeoutInSeconds (total/inactivity), already 600s, which is why the earlier ceiling bumps never addressed this failure. Phase B of #848; the durable fix (singleton Testcontainers Postgres + disabling the Spring Session JDBC cleanup scheduler in tests) follows. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>