h-vetinari commented on issue #35728: URL: https://github.com/apache/arrow/issues/35728#issuecomment-1560409997
Thanks @assignUser for chiming in! Some more context. It did not appear for the last successful [build](https://github.com/conda-forge/arrow-cpp-feedstock/pull/1042) of 12.0.0, then appeared for a [migration](https://github.com/conda-forge/arrow-cpp-feedstock/pull/1053) (of simultaneously re2, aws-crt & google-cloud-cpp; because reasons...), but only on linux, and not for any of the older arrow versions (which received the same migrator PRs). > Single test failure here, and only on linux. Normally I'd go with a skip, but this looks like it might be leaking memory? Any ideas? The test in question [has no](https://github.com/apache/arrow/blob/apache-arrow-12.0.0/python/pyarrow/tests/test_array.py#L40-L41) comments or documentation AFAICS. > > ``` > =================================== FAILURES =================================== > __________________________ test_total_bytes_allocated __________________________ > > def test_total_bytes_allocated(): > > assert pa.total_allocated_bytes() == 0 > E assert 1216 == 0 > E + where 1216 = <built-in function total_allocated_bytes>() > E + where <built-in function total_allocated_bytes> = pa.total_allocated_bytes > ``` > > It's also interesting that this doesn't appear in any of the equivalent PRs to the maintenance branches, e.g. #1057. However, I've now restarted https://github.com/conda-forge/arrow-cpp-feedstock/pull/1053, and although I have no idea why, the failure seems to have disappeared! 🥳 I'm happy to close this issue (and apologise for the noise), unless people want to leave this open a bit longer to understand better what's happening with `test_total_bytes_allocated`. As I mentioned above, it's hard to tell for me (from lack of code comments/context) what this test is actually testing, under which conditions it may fail, and how serious that is if it happens. -- 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]
