=dev-python/cheroot-10.0.1 is failing its test suite on one machine, which is trying to finish the Python 3.12 transition. (It built and installed without seeing this failure on another machine.) Here's the failure summary from the log: =========================================================== short test summary info ============================================================ XFAIL cheroot/test/test_core.py::test_large_request - https://github.com/cherrypy/cheroot/issues/106 XFAIL cheroot/test/test_conn.py::test_598 - Sometimes this test fails due to low timeout. Ref: https://github.com/cherrypy/cherrypy/issues/598 XFAIL cheroot/test/test_conn.py::test_Chunked_Encoding - Headers from earlier request leak into the request line for a subsequent request, resulting in 400 instead of 413. See cherrypy/cheroot#69 for details. FAILED cheroot/test/test_server.py::test_peercreds_unix_sock[abstract] - requests.exceptions.InvalidURL: Not supported URL scheme http+unix FAILED cheroot/test/test_server.py::test_peercreds_unix_sock[file] - requests.exceptions.InvalidURL: Not supported URL scheme http+unix FAILED cheroot/test/test_server.py::test_peercreds_unix_sock_with_lookup[abstract] - requests.exceptions.InvalidURL: Not supported URL scheme http+unix FAILED cheroot/test/test_server.py::test_peercreds_unix_sock_with_lookup[file] - requests.exceptions.InvalidURL: Not supported URL scheme http+unix ======================================= 4 failed, 169 passed, 3 xfailed, 23 warnings in 81.22s (0:01:21) ======================================= The error message in the failing tests is one I also saw in dev-python/requests-unixsocket, which I reported as bug #936014.
Created attachment 897553 [details] dev-python:cheroot-10.0.1:20240713-202507.log
Created attachment 897554 [details] emerge-info.txt
Did you try reinstalling requests-unixsocket?
Yes, I've tried that. I note that on this machine requests-unixsocket fails *its* tests with similar messages about "Not supported URL scheme http+unix" (bug #936014), so I expect that any solution for the underlying issue there will probably fix these tests as well.
