[GitHub] [arrow] pitrou commented on issue #35636: [CI][C++] Nightly test-conda-cpp-valgrind is flaky due to arrow-compute-vector-test taking closer to 500 seconds

["pitrou (via GitHub)" <gi...@apache.org>]

pitrou commented on issue #35636:
URL: https://github.com/apache/arrow/issues/35636#issuecomment-1609626613

   @raulcd Someone should ideally take a look into it and try to reduce the runtime under Valgrind.
   
   For example, it's not obvious that testing all datatypes exhaustively with random input is useful (why all integers, both signed and unsigned, for example?). Test sizes could also be reduced a bit.
   
   @felipecrv Since you've been working quite a bit on kernels, would you like to take a look at this?
   Note that you can use Archery to run the Valgrind CI job, for example `archery docker run conda-cpp-valgrind`.
   I would recommended shelling in the Docker image, though (`archery docker run conda-cpp-valgrind bash`), allowing you to build and test more selectively.
   


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org