[C++] Failure in jemalloc stats tests

[asfimport]

I just got this when running the tests locally:

[----------] 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)

It looks like those checks should be relaxed to allow for more context-dependent behaviour.

Reporter: Antoine Pitrou / @pitrou
Assignee: Antoine Pitrou / @pitrou
Watchers: Rok Mihevc / @rok

Related issues:

• [C++] Expose jemalloc statistics for logging (is caused by)

PRs and other links:

• GitHub Pull Request #14194

_{Note: This issue was originally created as ARROW-17800. Please see the migration documentation for further details.}

[asfimport]

Antoine Pitrou / @pitrou:
Also another failure on a CI job here:
https://github.com/ursacomputing/crossbow/actions/runs/3099075703/jobs/5017771117#step:5:2587

[----------] 2 tests from Jemalloc
[ RUN      ] Jemalloc.SetDirtyPageDecayMillis
[       OK ] Jemalloc.SetDirtyPageDecayMillis (0 ms)
[ RUN      ] Jemalloc.GetAllocationStats
/arrow/cpp/src/arrow/memory_pool_test.cc:188: Failure
Failed
'_error_or_value3.status()' failed with IOError: Failed retrieving 0xff9b69c4. Detail: [errno 22] Invalid argument
[  FAILED  ] Jemalloc.GetAllocationStats (0 ms)
[----------] 2 tests from Jemalloc (0 ms total)

[asfimport]

Rok Mihevc / @rok:
I'll open a PR in a minute.

[asfimport]

Rok Mihevc / @rok:
Except if you already started that is.

[asfimport]

Antoine Pitrou / @pitrou:
Indeed :-)

[asfimport]

Antoine Pitrou / @pitrou:
Issue resolved by pull request 14194
#14194