[ https://issues.apache.org/jira/browse/ARROW-17800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Pitrou resolved ARROW-17800. ------------------------------------ Resolution: Fixed Issue resolved by pull request 14194 [https://github.com/apache/arrow/pull/14194] > [C++] Failure in jemalloc stats tests > ------------------------------------- > > Key: ARROW-17800 > URL: https://issues.apache.org/jira/browse/ARROW-17800 > Project: Apache Arrow > Issue Type: Bug > Components: C++ > Reporter: Antoine Pitrou > Assignee: Antoine Pitrou > Priority: Critical > Labels: pull-request-available > Fix For: 10.0.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > I just got this when running the tests locally: > {code} > [----------] 2 tests from Jemalloc > [ RUN ] Jemalloc.SetDirtyPageDecayMillis > [ OK ] Jemalloc.SetDirtyPageDecayMillis (0 ms) > [ RUN ] Jemalloc.GetAllocationStats > /home/antoine/arrow/dev/cpp/src/arrow/memory_pool_test.cc:218: Failure > The difference between metadata0 and 3000000 is 2962256, which exceeds > 1000000, where > metadata0 evaluates to 5962256, > 3000000 evaluates to 3000000, and > 1000000 evaluates to 1000000. > [ FAILED ] Jemalloc.GetAllocationStats (0 ms) > [----------] 2 tests from Jemalloc (0 ms total) > {code} > It looks like those checks should be relaxed to allow for more > context-dependent behaviour. -- This message was sent by Atlassian Jira (v8.20.10#820010)