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/06/11 19:36:00 UTC
[jira] [Commented] (ARROW-5270) [C++] Reenable Valgrind on
Travis-CI
[ https://issues.apache.org/jira/browse/ARROW-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861398#comment-16861398 ]
Antoine Pitrou commented on ARROW-5270:
---------------------------------------
We now test with ASAN and UBSAN on Travis, so perhaps this is not as important as it used to be. [~wesmckinn][~emkornfield@gmail.com] opinions?
> [C++] Reenable Valgrind on Travis-CI
> ------------------------------------
>
> Key: ARROW-5270
> URL: https://issues.apache.org/jira/browse/ARROW-5270
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, Continuous Integration
> Reporter: Antoine Pitrou
> Priority: Critical
> Labels: pull-request-available
> Fix For: 0.14.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Running Valgrind on Travis-CI was disabled in ARROW-4611 (apparently because of issues within the re2 library).
> We should reenable it at some point in order to exercise the reliability of our C++ code.
> (and/or have a build with another piece of instrumentation enabled such as ASAN)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)