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/12/14 04:07:00 UTC

[jira] [Created] (ARROW-4026) [C++] Use separate modular $COMPONENT-test targets for unit tests

Wes McKinney created ARROW-4026:
-----------------------------------

             Summary: [C++] Use separate modular $COMPONENT-test targets for unit tests
                 Key: ARROW-4026
                 URL: https://issues.apache.org/jira/browse/ARROW-4026
             Project: Apache Arrow
          Issue Type: Improvement
          Components: C++
            Reporter: Wes McKinney
             Fix For: 0.12.0


Because some tests depend on libraries from another component (e.g. "gandiva" relies on "arrow"), if we build "gandiva" and {{ARROW_BUILD_TESTS=ON}} then we must also built the tests attached to the "arrow" target. This can be hacked around using the {{ARROW_TEST_INCLUDE_LABELS}} option, but the best thing would probably be to create separate modular targets for the unit tests:

* "arrow-tests" depends on "arrow"
* "parquet-tests" depends on "parquet", "arrow"
* "gandiva-test" depends on "gandiva", "arrow"



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