ZeliardM a679bc516f Stop Windows test runs from running out of loopback ports (#1839) ...

Windows has no native socketpair, so the self-pipe of every asyncio event
loop is a loopback TCP connection, and closing it leaves a port in
TIME_WAIT for two minutes. With a new event loop for each test, a run
that gets through about 16,000 tests within two minutes uses up the
dynamic port range, and the Windows test jobs hang until the 6-hour job
limit.

This PR runs the tests on one event loop per session, so a full run
opens about 100 socket pairs instead of about 26,000, and runs the
Windows jobs with xdist again.

In details:
- `asyncio_default_fixture_loop_scope` and
  `asyncio_default_test_loop_scope` are `session`.
- CI: Windows runs `pytest -n auto` like the other OSes, and the test
  jobs get a 30-minute limit.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

2026-11-06 18:50:15 -05:00

..

ci.yml

Stop Windows test runs from running out of loopback ports (#1839)

2026-11-06 18:50:15 -05:00

codeql-analysis.yml

Add Python 3.15 to supported versions and update pins (#1793)

2026-10-25 18:58:32 +01:00

publish.yml

Add Python 3.15 to supported versions and update pins (#1793)

2026-10-25 18:58:32 +01:00

release-draft.yml

Generate the changelog with git-cliff and draft releases in CI (#1809)

2026-10-24 16:24:08 +02:00

stale.yml

Add Python 3.15 to supported versions and update pins (#1793)

2026-10-25 18:58:32 +01:00