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
CI: the Test job is approaching its 30-minute timeout; parallelise the suite #383
Each test job on main now takes 20–23 minutes, against the 30-minute timeout-minutes in .github/workflows/test.yml, and the time grows as the suite grows. #375 and #372 both pushed the 3.10/3.11 jobs past the limit, and the jobs were cancelled rather than failed.
Proposal: run the suite in parallel with pytest-xdist (-n auto), or shard it across matrix jobs, rather than raising the timeout. Tests that depend on process-global state (environment, cwd, singleton lock, launch-directory capture) would need to be marked to run serially or isolated per worker. Raising the limit only postpones the problem.
Not urgent before 3.0.0, but every large PR will hit it.
Stopgap merged in #384 (f15c975): the test job timeout and the workflow guard ceiling are now 45 minutes. This issue stays open for the real fix, parallelising the suite.
Measurement from #388 (the #297 validation-echo implementation): it adds about 274 s to the 3.10 suite on ai, with coverage (base f9f4bd0 1030 s, head 482f281 1304 s). That projects to about 6–7 more minutes per CI test job, roughly 30 min in total against the 45-min limit from #384. About 51 s of that is spread over existing subprocess tests, because import pmcp now imports the MCP SDK. The headroom is shrinking, so parallelising the suite here is the durable fix.
Resolved on main by #399 (1dd222f), following the Python 3.12 matrix trim in #397 (2944b1e). The test job now runs pytest-xdist with -n auto --dist loadfile. Remaining timing-oracle robustness work stays tracked separately in #400 and #311.
Activity
ci: raise the workflow guard's timeout ceiling to 45 to match (see #383)
ci: raise the test job timeout and the workflow guard ceiling to 45 m…
ViperJuice commentedon Oct 8, 2026
Stopgap merged in #384 (f15c975): the test job timeout and the workflow guard ceiling are now 45 minutes. This issue stays open for the real fix, parallelising the suite.
ci(release): the release build gets 45 minutes and full history with …
ViperJuice commentedon Oct 10, 2026
Measurement from #388 (the #297 validation-echo implementation): it adds about 274 s to the 3.10 suite on ai, with coverage (base f9f4bd0 1030 s, head 482f281 1304 s). That projects to about 6–7 more minutes per CI test job, roughly 30 min in total against the 45-min limit from #384. About 51 s of that is spread over existing subprocess tests, because
import pmcpnow imports the MCP SDK. The headroom is shrinking, so parallelising the suite here is the durable fix.test: observe group kills independently of asyncio reaping (see #383)
test: make parallel checks independent of reaping and scheduling (see #…
test: check redactor cost growth across input sizes (see #383)
ci: parallelize the full test suite by file (see #383)
ViperJuice commentedon Oct 17, 2026
Resolved on main by #399 (1dd222f), following the Python 3.12 matrix trim in #397 (2944b1e). The test job now runs pytest-xdist with -n auto --dist loadfile. Remaining timing-oracle robustness work stays tracked separately in #400 and #311.