Bug 933098 – dev-python/pytest-subprocess-1.5.0 fails tests

• Product: Gentoo Linux
• Status: UNCONFIRMED ---

[Description Jonathan Lovelace 2024-05-29 02:24:40 UTC]

Created attachment 894583 [details]
dev-python:pytest-subprocess-1.5.0:20240529-021706.log

=dev-python/pytest-subprocess-1.5.0 fails its tests on my machine, with the following failures:

=========================================================================== short test summary info ============================================================================
SKIPPED [4] tests/test_asyncio.py:114: condition: sys.platform!="win32"
FAILED tests/test_subprocess.py::test_basic_process[str-False] - AttributeError: 'tuple' object has no attribute 'communicate'
FAILED tests/test_subprocess.py::test_basic_process[path,str-False] - AttributeError: 'tuple' object has no attribute 'communicate'
FAILED tests/test_subprocess.py::test_basic_process[str,path-False] - AttributeError: 'tuple' object has no attribute 'communicate'
FAILED tests/test_subprocess.py::test_basic_process[path-False] - AttributeError: 'tuple' object has no attribute 'communicate'
FAILED tests/test_subprocess.py::test_basic_process_merge_streams[False] - AttributeError: 'tuple' object has no attribute 'communicate'
FAILED tests/test_subprocess.py::test_wait[False] - AttributeError: 'tuple' object has no attribute 'returncode'
FAILED tests/test_subprocess.py::test_check_output[False] - TypeError: 'tuple' object does not support the context manager protocol
FAILED tests/test_subprocess.py::test_check_call[False] - TypeError: 'tuple' object does not support the context manager protocol
FAILED tests/test_subprocess.py::test_call[False] - TypeError: 'tuple' object does not support the context manager protocol
FAILED tests/test_subprocess.py::test_run[False] - TypeError: 'tuple' object does not support the context manager protocol
FAILED tests/test_subprocess.py::test_universal_newlines[False] - AttributeError: 'tuple' object has no attribute 'wait'
FAILED tests/test_subprocess.py::test_text[False] - AttributeError: 'tuple' object has no attribute 'wait'
FAILED tests/test_subprocess.py::test_input[False] - AttributeError: 'tuple' object has no attribute 'communicate'
FAILED tests/test_subprocess.py::test_ambiguous_input[False] - TypeError: 'tuple' object does not support the context manager protocol
FAILED tests/test_subprocess.py::test_multiple_wait[False] - AttributeError: 'tuple' object has no attribute 'wait'
FAILED tests/test_subprocess.py::test_use_real - TypeError: 'tuple' object does not support the context manager protocol
FAILED tests/test_subprocess.py::test_real_process - TypeError: 'tuple' object does not support the context manager protocol
FAILED tests/test_subprocess.py::test_encoding[False-encoding] - TypeError: 'tuple' object does not support the context manager protocol
FAILED tests/test_subprocess.py::test_encoding[False-errors] - TypeError: 'tuple' object does not support the context manager protocol
FAILED tests/test_subprocess.py::test_allow_unregistered_cleaning - TypeError: 'tuple' object does not support the context manager protocol
FAILED tests/test_subprocess.py::test_non_piped_streams[True-False] - AttributeError: 'tuple' object has no attribute 'communicate'
FAILED tests/test_subprocess.py::test_non_piped_streams[False-False] - AttributeError: 'tuple' object has no attribute 'communicate'
FAILED tests/test_subprocess.py::test_non_piped_same_file[True-False] - AttributeError: 'tuple' object has no attribute 'communicate'
FAILED tests/test_subprocess.py::test_non_piped_same_file[False-False] - AttributeError: 'tuple' object has no attribute 'communicate'
============================================================ 24 failed, 108 passed, 4 skipped, 27 warnings in 7.93s ============================================================

I tried searching the upstream issue tracker and Googling for the error messages.  There was an issue in the upstream issue tracker (https://github.com/aklajnert/pytest-subprocess/issues/149) where the attached log contained at least some of these failures (along with much more serious errors), but the last comment was the developer asking the reporter to try again because the latest master contained fixes for the headline isssue, and I tried applying the entire diff from version 1.5.0 to the latest master using /etc/portage/patches, and got the same failures. (The only results Google turned up were comments on unrelated StackOverflow questions, ending in a comment to the effect of "I found a solution" with no other explanation.)

[Comment 1 Jonathan Lovelace 2024-05-29 02:25:41 UTC]

Created attachment 894584 [details]
emerge-info.txt