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 2019/06/03 15:22:00 UTC
[jira] [Resolved] (ARROW-4504) [C++] Reduce the number of unit test
executables
[ https://issues.apache.org/jira/browse/ARROW-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wes McKinney resolved ARROW-4504.
---------------------------------
Resolution: Fixed
Issue resolved by pull request 4442
[https://github.com/apache/arrow/pull/4442]
> [C++] Reduce the number of unit test executables
> ------------------------------------------------
>
> Key: ARROW-4504
> URL: https://issues.apache.org/jira/browse/ARROW-4504
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Wes McKinney
> Assignee: Wes McKinney
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.14.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Link times are a significant drag in MSVC builds. They don't affect Linux nearly as much when building with Ninja. I suggest we combine some of the fast-running tests within logical units to see if we can cut down from 106 test executables to 70 or so
> {code}
> 100% tests passed, 0 tests failed out of 107
> Label Time Summary:
> arrow-tests = 21.19 sec*proc (48 tests)
> arrow_python-tests = 0.26 sec*proc (1 test)
> example = 0.05 sec*proc (1 test)
> gandiva-tests = 11.65 sec*proc (39 tests)
> parquet-tests = 35.81 sec*proc (18 tests)
> unittest = 68.92 sec*proc (106 tests)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)