You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@arrow.apache.org by "Antoine Pitrou (JIRA)" <ji...@apache.org> on 2019/01/03 20:54:00 UTC

[jira] [Resolved] (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:all-tabpanel ]

Antoine Pitrou resolved ARROW-4009.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 0.12.0

Issue resolved by pull request 3302
[https://github.com/apache/arrow/pull/3302]

> [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
>              Labels: pull-request-available
>             Fix For: 0.12.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> 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)