| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
The test patches PROCESS_TERMINATION_TIMEOUT so the spawned server can unwind, save its subprocess coverage data, and print the clean-exit line before the kill escalation. One heavily starved Windows CI runner stalled the child past the previous 10s grace, so it was killed before printing and the stderr assertion failed with empty output. The post-stdin-close tail is normally well under a second even on loaded Windows runners, so double the grace to 20s (and the outer fail_after to 30s); the grace wait returns as soon as the child exits, so passing runs are unaffected.
|
This pull request is included in pre-release v2.0.0a2 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Widens the stdio round-trip test's termination grace (10s → 20s) and its outer fail_after (20s → 30s) so a badly starved CI runner can't kill the child server before it writes the clean-exit line.
Motivation and Context
test_tool_call_and_notification_round_trip_over_a_stdio_subprocess patches PROCESS_TERMINATION_TIMEOUT so the spawned server has time, after stdin closes, to unwind, save its subprocess coverage data, and print stdio-echo: clean exit (the ordering #2840 established so a kill can't silently lose the coverage data). On one heavily contended run (3.13, lowest-direct, windows-latest, 2026-06-15) the runner stalled the child past the 10s grace; it was killed before printing and the test failed with an empty stderr capture.
Measurements on a loaded windows-latest runner with the same configuration (Python 3.13, lowest-direct, subprocess coverage, background pytest + CPU load) put the post-stdin-close tail at ~0.2s median / ~0.4s max — dominated by the coverage save — so the failure needed an extreme machine-level stall rather than anything systematic. Doubling the grace keeps that class of runner pathology from failing the leg, and costs nothing on healthy runs because the wait returns as soon as the child exits. A genuinely hung child still fails, just after 20s instead of 10s.
How Has This Been Tested?
Breaking Changes
None — test-only change; the production PROCESS_TERMINATION_TIMEOUT default (2.0s) is untouched.
Types of changes
Checklist
Additional context
Since #2773 and #2840 this is the only stdio test failure observed in CI (once across all runs and matrix legs since June 12), so this is a belt-and-braces margin bump rather than a fix for an active problem.
AI Disclaimer