Bug 834814

Summary:	dev-python/pytest-asyncio-0.19.0 fails tests on MUSL
Product:	Gentoo Linux	Reporter:	Agostino Sarubbo <ago>
Component:	Current packages	Assignee:	Python Gentoo Team <python>
Status:	CONFIRMED ---
Severity:	normal	CC:	m.seifert
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	build.log

Description Agostino Sarubbo gentoo-dev

2022-03-09 07:37:53 UTC

https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: dev-python/pytest-asyncio-0.17.2 fails tests.
Discovered on: amd64 (internal ref: tinderbox_musl)

NOTE:
This machine uses MUSL libc

Comment 1 Agostino Sarubbo gentoo-dev

2022-03-09 07:37:55 UTC

Created attachment 766621 [details]
build.log

build log and emerge --info

Comment 2 Agostino Sarubbo gentoo-dev

2022-03-09 07:37:55 UTC

Error(s) that match a know pattern:


E   OSError: [Errno 99] error while attempting to bind on address ('::1', 40779, 0, 0): address not available
E   OSError: [Errno 99] error while attempting to bind on address ('::1', 60647, 0, 0): address not available
FAILED tests/test_simple.py::test_unused_port_factory_fixture - OSError: [Err...
FAILED tests/test_simple.py::test_unused_port_fixture - OSError: [Errno 99] e...

Comment 3 Agostino Sarubbo gentoo-dev

2022-08-21 14:41:20 UTC

tinderbox_musl has reproduced this issue with version 0.19.0 - Updating summary.

Comment 4 Michael Seifert 2023-11-10 14:03:25 UTC

Pytest-asyncio contains some tests that attempt to call Python's socket.bind, which seems to trigger the error.

Is this blocked by FEATURES=network-sandbox? If so, why does it occur with MUSL only?