This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ERROR: test_config_queue_handler_multiprocessing_context (test.test_logging.ConfigDictTest.test_config_queue_handler_multiprocessing_context) (start_method='fork')
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/runner/work/cpython/cpython/Lib/test/test_logging.py", line 4014, in test_config_queue_handler_multiprocessing_context
q = manager.Queue()
File "/home/runner/work/cpython/cpython/Lib/multiprocessing/managers.py", line 729, in temp
token, exp = self._create(typeid, *args, **kwds)
~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
File "/home/runner/work/cpython/cpython/Lib/multiprocessing/managers.py", line 609, in _create
conn = self._Client(self._address, authkey=self._authkey)
File "/home/runner/work/cpython/cpython/Lib/multiprocessing/connection.py", line 525, in Client
answer_challenge(c, authkey)
~~~~~~~~~~~~~~~~^^^^^^^^^^^^
File "/home/runner/work/cpython/cpython/Lib/multiprocessing/connection.py", line 953, in answer_challenge
message = connection.recv_bytes(256) # reject large message
File "/home/runner/work/cpython/cpython/Lib/multiprocessing/connection.py", line 216, in recv_bytes
buf = self._recv_bytes(maxlength)
File "/home/runner/work/cpython/cpython/Lib/multiprocessing/connection.py", line 430, in _recv_bytes
buf = self._recv(4)
File "/home/runner/work/cpython/cpython/Lib/multiprocessing/connection.py", line 395, in _recv
chunk = read(handle, remaining)
ConnectionResetError: [Errno 104] Connection reset by peer
I don't know the exact reason but I assume it's because it's on emulated linux. Other tests that use multiprocessing queues were already disabled for (probably) the same reasons:
NB: I took the liberty of fixing a whitespace that I forgot.
NB2: the original issue is #121723 but I'm not sure whether I should put it in the title or not.
brandtbucher
changed the title
[CI/JIT] fix aarch64-unknown-linux-gnu logging tests
121723: Skip test_config_queue_handler_multiprocessing_context in emulated JIT CI
Aug 13, 2024
brandtbucher
changed the title
121723: Skip test_config_queue_handler_multiprocessing_context in emulated JIT CI
GH-121723: Skip test_config_queue_handler_multiprocessing_context in emulated JIT CI
Aug 13, 2024
brandtbucher
changed the title
GH-121723: Skip test_config_queue_handler_multiprocessing_context in emulated JIT CI
GH-121723: Skip test_config_queue_handler_multiprocessing_context in emulated JIT CI
Aug 13, 2024
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The test in question requires multiprocessing managers but the test failed since then:
https://github.com/python/cpython/actions/workflows/jit.yml
example logs: https://github.com/python/cpython/actions/runs/10358273944/job/28672370717
I don't know the exact reason but I assume it's because it's on emulated linux. Other tests that use multiprocessing queues were already disabled for (probably) the same reasons:
NB: I took the liberty of fixing a whitespace that I forgot.
NB2: the original issue is #121723 but I'm not sure whether I should put it in the title or not.