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 2018/12/12 19:50:00 UTC
[jira] [Commented] (ARROW-3803) [C++/Python] Split C++ and Python
unit test Travis CI jobs, run all C++ tests (including Gandiva) together
[ https://issues.apache.org/jira/browse/ARROW-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719366#comment-16719366 ]
Antoine Pitrou commented on ARROW-3803:
---------------------------------------
Note that C++ code coverage needs to be enabled when running the Python tests, too, as that covers some parts of the C++ source tree.
> [C++/Python] Split C++ and Python unit test Travis CI jobs, run all C++ tests (including Gandiva) together
> ----------------------------------------------------------------------------------------------------------
>
> Key: ARROW-3803
> URL: https://issues.apache.org/jira/browse/ARROW-3803
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, Python
> Reporter: Wes McKinney
> Priority: Major
> Fix For: 0.12.0
>
>
> Our main C++/Python job is bumping up against the 50 minute limit lately, so it is time to do a little bit of reorganization
> I suggest that we do this:
> * Build and test all C++ code including Gandiva in a single job on Linux and macOS
> * Run Python unit tests (but not the C++ tests) on Linux and macOS in a separate job
> Code coverage will need to get uploaded in the Linux jobs for both of these, so a little bit of surgery is required
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)