Open danceratopz opened 2 weeks ago
Now we are seeing a lot of these:
_ test_valid_inputs[fork_Cancun-blockchain_test-result_Result.SUCCESS-in_bounds_z] _
[gw2] linux -- Python 3.12.6 /home/runner/work/execution-spec-tests/execution-spec-tests/.tox/tests/bin/python3
.tox/tests/lib/python3.12/site-packages/urllib3/connectionpool.py:716: in urlopen
httplib_response = self._make_request(
.tox/tests/lib/python3.12/site-packages/urllib3/connectionpool.py:416: in _make_request
conn.request(method, url, **httplib_request_kw)
.tox/tests/lib/python3.12/site-packages/urllib3/connection.py:244: in request
super(HTTPConnection, self).request(method, url, body=body, headers=headers)
../../../.local/share/uv/python/cpython-3.12.6-linux-x86_64-gnu/lib/python3.12/http/client.py:1336: in request
self._send_request(method, url, body, headers, encode_chunked)
../../../.local/share/uv/python/cpython-3.12.6-linux-x86_64-gnu/lib/python3.12/http/client.py:1382: in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
../../../.local/share/uv/python/cpython-3.12.6-linux-x86_64-gnu/lib/python3.12/http/client.py:1331: in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
../../../.local/share/uv/python/cpython-3.12.6-linux-x86_64-gnu/lib/python3.12/http/client.py:1091: in _send_output
self.send(msg)
../../../.local/share/uv/python/cpython-3.12.6-linux-x86_64-gnu/lib/python3.12/http/client.py:1035: in send
self.connect()
.tox/tests/lib/python3.12/site-packages/requests_unixsocket/adapters.py:35: in connect
sock.connect(socket_path)
E ConnectionRefusedError: [Errno 111] Connection refused
I've seen at least two instances where the failure is marked on the first two tests:
4 workers [6318 items]
FF................................................................. [ 67/6318]
But I'm not sure if this is a pytest artifact or is it really the first two tests that are consistently failing.
850 consistently failed
tox_verify
with the Python 3.10 config in the test env with the following test:The error points to a resolver timeout:
The strange thing is that it only failed on 3.10, even though both the 3.10 and 3.12 matrix configs both run on Ubuntu. macOS seems fine (with 3.12). It wasn't reproducible locally with 3.10. As a result, the following matrix config has been temporarily disabled pending resolution, see #850.
This matrix config never saw a fail: