On Sun, Dec 22, 2024 at 10:13:01AM +0100, Lucas Nussbaum wrote: > > =================================== FAILURES > > =================================== > > _______________ TestSOCKS4Proxy.test_socks_with_invalid_username > > _______________ [...] > > > with pytest.raises(NewConnectionError, match="different > > > user-ids"): > > E AssertionError: Regex pattern did not match. > > E Regex: 'different user-ids' > > E Input: '<urllib3.contrib.socks.SOCKSConnection object at > > 0x7f3afc1a6570>: Failed to establish a new connection: [Errno 111] > > Connection refused' > > > > test/contrib/test_socks.py:724: AssertionError > > ------------------------------ Captured log call > > ------------------------------- > > DEBUG urllib3.util.retry:retry.py:286 Converted retries value: False -> > > Retry(total=False, connect=None, read=None, redirect=0, status=None) > > DEBUG urllib3.connectionpool:connectionpool.py:243 Starting new HTTP > > connection (1): example.com:80 > > DEBUG socks:socks.py:799 Error connecting to SOCKS4 proxy > > localhost:38485 due to: [Errno 111] Connection refused
I haven't been able to reproduce this in sbuild with --chroot-mode=unshare and --no-enable-network, although that usually shakes out this kind of thing. (Besides, the proxy it's failing to connect to here is on localhost.) Can you still reproduce it? If so, I'm somewhat tempted to disable the test as flaky, although if there's some way I can reproduce it locally I'm willing to try debugging it. (You may run into the issue I filed upstream as https://github.com/urllib3/urllib3/pull/3547, but I think that's separate.) Thanks, -- Colin Watson (he/him) [cjwat...@debian.org]
