You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Antoine Pitrou (Jira)" <ji...@apache.org> on 2022/09/21 13:43:00 UTC
[jira] [Assigned] (ARROW-17800) [C++] Failure in jemalloc stats tests
[ https://issues.apache.org/jira/browse/ARROW-17800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Pitrou reassigned ARROW-17800:
--------------------------------------
Assignee: Rok Mihevc
> [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: Rok Mihevc
> Priority: Critical
> Fix For: 10.0.0
>
>
> 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)