setup.py | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 relax cython dependency

tests/test_unix.py | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 relax timeout limit for riscv64 so tests could finish

tests/test_aiohttp.py | 30 20 + 10 - 0 !
tests/test_context.py | 41 31 + 10 - 0 !
tests/test_regr1.py | 7 5 + 2 - 0 !
tests/test_signals.py | 8 4 + 4 - 0 !
tests/test_udp.py | 74 56 + 18 - 0 !
uvloop/_testbase.py | 15 13 + 2 - 0 !
6 files changed, 129 insertions(+), 46 deletions(-)

 fix unit tests on ipv6-only hosts

This patch modifies the included unit test scripts to complete successfully
on IPv6-only hosts, as well as IPv4-only hosts and dual-stack hosts.

tests/test_dns.py | 2 2 + 0 - 0 !
1 file changed, 2 insertions(+)

 skip tests failing with libuv 1.48.0

Bug: https://github.com/MagicStack/uvloop/issues/596

tests/test_base.py | 11 8 + 3 - 0 !
1 file changed, 8 insertions(+), 3 deletions(-)

 compensate for asyncio changes in python 3.13.3/3.14

In
https://github.com/python/cpython/commit/38a99568763604ccec5d5027f0658100ad76876f
(backported to 3.13 as
https://github.com/python/cpython/commit/7b0543ebe649aea11531e994289293f23f41064e),
Python moved the responsibility for setting the task name from
`asyncio.create_task` to the `Task` constructor.  While `uvloop` itself
is unaffected, this causes `test_set_task_name` to fail when run with
`asyncio`.  Compensate for that in this particular test.

It's possible that `uvloop`'s behaviour should be changed to match
`asyncio`'s depending on the Python version, but that seems like a more
involved change.  For now, this at least gets the tests passing again.

Most of this analysis and patch were from Martin Hostettler in
https://bugs.debian.org/1101258#24; I just tweaked the patch slightly to
ensure it still passes on older Python versions.