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 2018/10/04 12:08:00 UTC

[jira] [Assigned] (ARROW-3254) [C++] Add option to ADD_ARROW_TEST to compose a test executable from multiple .cc files containing unit tests

     [ https://issues.apache.org/jira/browse/ARROW-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wes McKinney reassigned ARROW-3254:
-----------------------------------

    Assignee: Wes McKinney

> [C++] Add option to ADD_ARROW_TEST to compose a test executable from multiple .cc files containing unit tests
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: ARROW-3254
>                 URL: https://issues.apache.org/jira/browse/ARROW-3254
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Wes McKinney
>            Assignee: Wes McKinney
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.12.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently there is a 1-1 correspondence between a .cc file containing unit tests to a test executable. There's good reasons (like readability, code organization) to split up a large test suite among many files. But there are downsides:
> * Linking test executables is slow, especially on Windows
> * Test executables take up quite a bit of space (the debug/ directory on Linux after a full build is ~1GB)
> I suggest enabling ADD_ARROW_TEST to accept a list of files which will be build together into a single test. This will allow us to combine a number of our unit tests and save time and space



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)