Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
Observed on master and many PRs, example: https://github.com/apache/arrow/runs/6991997196?check_suite_focus=true
From a quick read, it's likely just that the stderr isn't necessarily empty as the test expects.
=================================== FAILURES ===================================
_____________ test_debug_memory_pool_disabled[system_memory_pool] ______________
pool_factory = <built-in function system_memory_pool>
@pytest.mark.parametrize('pool_factory', supported_factories())
def test_debug_memory_pool_disabled(pool_factory):
res = run_debug_memory_pool(pool_factory.__name__, "")
# The subprocess either returned successfully or was killed by a signal
# (due to writing out of bounds), depending on the underlying allocator.
if os.name == "posix":
assert res.returncode <= 0
else:
res.check_returncode()
> assert res.stderr == ""
E assert 'Fatal Python...in <module>\n' == ''
E + Fatal Python error: Segmentation fault
E +
E + Current thread 0x0000000102009e00 (most recent call first):
E + File "<string>", line 12 in <module>
/usr/local/lib/python3.9/site-packages/pyarrow/tests/test_memory.py:245: AssertionError
Attachments
Issue Links
- links to
