[
https://issues.apache.org/jira/browse/KUDU-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634427#comment-15634427
]
Todd Lipcon commented on KUDU-1740:
-----------------------------------
We can run them in parallel for pre-commit by just adding them to the list
where dist-test determines the number of test shards. That seems better than
splitting the tests up IMO since splitting to multiple executables increases
build time for static-linked build types.
> Split the kudu-tool-test into multiple binaries
> -----------------------------------------------
>
> Key: KUDU-1740
> URL: https://issues.apache.org/jira/browse/KUDU-1740
> Project: Kudu
> Issue Type: Test
> Components: test
> Reporter: Dinesh Bhat
> Assignee: Dinesh Bhat
> Priority: Trivial
>
> Per Mike's comment here, it would be good to split existing kudu-tool-test
> into multiple files so that we can take advantage of running some of these
> tests in parallel. Also, as the test suite is getting bigger, it reduces the
> overall test run time as well. We can leverage this cleanup to migrate all
> the tool related tests we have under kudu-admin-test.
> https://gerrit.cloudera.org/#/c/4834/6/src/kudu/tools/kudu-tool-test.cc
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
