<feed xmlns='http://www.w3.org/2005/Atom'>
<title>meshbay.git/conftest.py, branch 0.14</title>
<subtitle>MeshBay — read-only public mirror</subtitle>
<id>https://git.meshbay.org/meshbay.git/atom?h=0.14</id>
<link rel='self' href='https://git.meshbay.org/meshbay.git/atom?h=0.14'/>
<link rel='alternate' type='text/html' href='https://git.meshbay.org/meshbay.git/'/>
<updated>2026-09-03T23:47:26Z</updated>
<entry>
<title>test: add pytest-timeout and pin the Windows selector event loop</title>
<updated>2026-09-03T23:47:26Z</updated>
<author>
<name>Christophe Besson</name>
<email>cbesson@gmail.com</email>
</author>
<published>2026-09-03T23:47:26Z</published>
<link rel='alternate' type='text/html' href='https://git.meshbay.org/meshbay.git/commit/?id=a5255ec984098579d400a631fdf3a2571cb0ca79'/>
<id>urn:sha1:a5255ec984098579d400a631fdf3a2571cb0ca79</id>
<content type='text'>
A hung test could wedge the whole run: aiortc's ICE stack never completes
a loopback DataChannel handshake on Windows' default ProactorEventLoop, and
nothing capped it. Two changes, both no-ops off Windows:

- `timeout = 60` in the root pytest config (+ pytest-timeout in the dev
  extras) so a stall fails the test instead of the suite.
- a root conftest that selects WindowsSelectorEventLoopPolicy on win32 only,
  which is what aiortc needs there. Trade-off, documented: the selector loop
  cannot spawn subprocesses on Windows, so the ffmpeg streaming tests fail
  there rather than pass -- they need a per-module override or skipif(win32).

Co-Authored-By: Claude Sonnet 5 &lt;noreply@anthropic.com&gt;
</content>
</entry>
</feed>
