apache
ARROW-17207: [C++][CI] Occasional timeout failures on arrow-compute-scalar-test
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
:warning: Ticket has not been started in JIRA, please click 'Start Progress'.
No single test dominates the execution time. There are just a lot of tests. None of the tests appear to use threads. When run with TSAN the tests are slower but the additional load appears evenly distributed across tests.
Splitting into two tests seems like the simplest approach for now.
While the approach here is sane, perhaps we can try profiling this with TSAN enabled to see if there obvious optimizations to do in our test routines?
(another possibility might be to enable some compiler optimizations when building with TSAN, I don't think how safe/reasonable that is)
Alternative is to simply bump the timeout a bit: https://github.com/apache/arrow/pull/14502
Now that https://github.com/apache/arrow/pull/14502 is merged, I think we can close this.
Note I also profiled as I suggested above (albeit without TSAN), and unfortunately no particular contributor stood out.