[ARROW-4009] [CI] Run Valgrind and C++ code coverage in different bulds

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.11.1
• Fix Version/s: 0.12.0
• Component/s: C++, Continuous Integration
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/20611
• Assignee: Antoine Pitrou
• Reporter: Antoine Pitrou
• Created: 12/Dec/18 19:38
• Updated: 11/Jan/23 07:31
• Resolved: 03/Jan/19 20:53

Description

Currently, we run Valgrind on a coverage-enabled C++ build on Travis-CI. This means the slowness of Valgrind acts as a multiplier of the overhead of outputting coverage information using the instrumentation added by the compiler.

Instead we should probably emit C++ (and Python) coverage information in a different Travis-CI build without Valgrind enabled.

Issue Links

• links to: GitHub Pull Request #3302