[openbsd] tests/test_regr1.py::TestIssue39Regr::test_issue39_regression hangs inifinitely

Nobody has claimed this yet.

* **uvloop version**: 0.20.0
* **Python version**: 3.11.9
* **Platform**: OpenBSD
* **Can you reproduce the bug with `PYTHONASYNCIODEBUG` in env?**: Yes
* **Does uvloop behave differently from vanilla asyncio? How?**:

Output for testing that one test, but have to manually kill as there is no output in the logs or console:
```
===> Regression tests for py3-uvloop-0.20.0
cd /usr/ports/pobj/py-uvloop-0.20.0-python3/uvloop-0.20.0 && env PYTHONASYNCIODEBUG=1 py.test -vvv tests/test_regr1.py
============================= test session starts ==============================
platform openbsd7 -- Python 3.11.9, pytest-8.2.0, pluggy-1.5.0 -- /usr/local/bin/python3.11
cachedir: .pytest_cache
rootdir: /usr/ports/pobj/py-uvloop-0.20.0-python3/uvloop-0.20.0
configfile: pyproject.toml
collecting ... collected 1 item

tests/test_regr1.py::TestIssue39Regr::test_issue39_regression ^C*** Signal SIGINT in . (/usr/ports/pobj/py-uvloop-0.20.0-python3/.test_done)
*** Error 1 in /usr/ports/devel/py-uvloop (/usr/ports/infrastructure/mk/bsd.port.mk:2704 'test': @lock=py3-uvloop-0.20.0; export _LOCKS_HEL...)
```

Start with tests/test_regr1.py::TestIssue39Regr::test_issue39_regression and reproduce it on OpenBSD using the reported pytest command with PYTHONASYNCIODEBUG=1. Compare the behavior with vanilla asyncio as requested in the issue, then use the test and its output to identify what prevents termination. Done means the regression test completes without requiring manual interruption on the reported environment.

Written by the indexing model from the issue text.