[
https://issues.apache.org/jira/browse/ARROW-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733284#comment-16733284
]
Wes McKinney commented on ARROW-4009:
-------------------------------------
I think this is OK for now -- we should look more seriously at moving valgrind
runs to dedicated hardware (ie Jenkins) where we can request builds using a
bot.
> [CI] Run Valgrind and C++ code coverage in different bulds
> ----------------------------------------------------------
>
> Key: ARROW-4009
> URL: https://issues.apache.org/jira/browse/ARROW-4009
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, Continuous Integration
> Affects Versions: 0.11.1
> Reporter: Antoine Pitrou
> Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
