[
https://issues.apache.org/jira/browse/ARROW-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722300#comment-16722300
]
Wes McKinney commented on ARROW-3803:
-------------------------------------
[~fsaintjacques] I've already addressed that particular issue in the other
patches this week. The builds are faster now so this has grown somewhat less
urgent since things aren't timing out as much now
Now the main issue is that we have the C++ unit tests split between two builds
-- we may have to wait until the valgrind failures in Gandiva are fixed cc
[~pravindra]
> [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)
