h-vetinari commented on PR #37624:
URL: https://github.com/apache/arrow/pull/37624#issuecomment-1722731322
There's one failure in one job, which is flaky however:
```
=================================== 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 AssertionError: assert 'libc++abi: P...ion called!\n' == ''
E + libc++abi: Pure virtual function called!
pyarrow/tests/test_memory.py:255: AssertionError
----------------------------- Captured stderr call
-----------------------------
libc++abi: Pure virtual function called!
```
Generally, tests that kill other subprocesses by a signal are hard to make
100% reliable. I wouldn't mind skipping this one, but in any case, it has
nothing to do with this PR - those kind of transient failures happen
unpredictably.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
