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
Reporter: Wes McKinney / @wesm
Assignee: Antoine Pitrou / @pitrou
Related issues:
PRs and other links:
Note: This issue was originally created as ARROW-3254. Please see the migration documentation for further details.
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
Reporter: Wes McKinney / @wesm
Assignee: Antoine Pitrou / @pitrou
Related issues:
PRs and other links:
Note: This issue was originally created as ARROW-3254. Please see the migration documentation for further details.