Skip to content

Commit 3b6f9ab

Browse files
rustyconoverclaude
andcommitted
Use a finite connection cap for the shared fixture workers
Worker.main's --max-connections refuses 0, so the catalog fixture worker exited at startup under the launcher. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1 parent 5ab014a commit 3b6f9ab

1 file changed

Lines changed: 5 additions & 4 deletions

File tree

‎tests/conftest.py‎

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -45,10 +45,11 @@ def _fixture_command(*argv: str) -> str:
4545
"""Return the ``Client`` worker string for a fixture command under ``TEST_TRANSPORT``."""
4646
if TEST_TRANSPORT == "subprocess":
4747
return shlex.join(argv)
48-
# Every test process shares the one worker, so it must not cap connections:
49-
# at the default 64 a scan holding its connections while its next one waits
50-
# in the backlog can wait on the others doing the same, forever.
51-
launch_argv = [shutil.which(argv[0]) or argv[0], *argv[1:], "--max-connections", "0"]
48+
# Every test process shares the one worker, so its connection cap must sit
49+
# above anything the suite opens: at the default 64 a scan holding its
50+
# connections while its next one waits in the backlog can wait on the others
51+
# doing the same, forever. Finite because ``Worker.main`` refuses 0.
52+
launch_argv = [shutil.which(argv[0]) or argv[0], *argv[1:], "--max-connections", "4096"]
5253
_LAUNCHED.append(launch_argv)
5354
return "launch:" + shlex.join(launch_argv)
5455

0 commit comments

Comments
 (0)