[GitHub] [arrow] westonpace commented on issue #33699: [CI][C++] Nightly tests for valgrind have been failing for the last

westonpace commented on issue #33699: URL: https://github.com/apache/arrow/issues/33699#issuecomment-1398508810 Alternatively, we could try reducing the runtime of these tests when valgrind is enabled. `parquet-arrow-test` for example tries many different type variations (8 different

[GitHub] [arrow] westonpace commented on issue #33699: [CI][C++] Nightly tests for valgrind have been failing for the last

westonpace commented on issue #33699: URL: https://github.com/apache/arrow/issues/33699#issuecomment-1398505553 I tried looking into this a bit more today. I ran the `parquet-reader-test` on master, on the same commit that last passed (df4cb9588) and on a really old commit

[GitHub] [arrow] westonpace commented on issue #33699: [CI][C++] Nightly tests for valgrind have been failing for the last

westonpace commented on issue #33699: URL: https://github.com/apache/arrow/issues/33699#issuecomment-1384138560 This is an odd collection of tests. I don't think I've ever seen `arrow-compute-union-node-test` fail and `parquet-reader-test` doesn't really fit in with the mix. Note that