You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2018/12/12 19:48:00 UTC
[jira] [Commented] (ARROW-4009) [CI] Run Valgrind and C++ code
coverage in different bulds
[ https://issues.apache.org/jira/browse/ARROW-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719363#comment-16719363 ]
Wes McKinney commented on ARROW-4009:
-------------------------------------
I would prefer to do ARROW-3803 if we can first (consolidate C++ tests in their own build, and Python tests in their own build)
> [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)