You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2020/06/02 13:36:00 UTC

[jira] [Resolved] (KUDU-1740) Split the kudu-tool-test into multiple binaries

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

Grant Henke resolved KUDU-1740.
-------------------------------
    Fix Version/s: NA
       Resolution: Fixed

We shard the tests to run them in parallel.

> 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
>             Fix For: NA
>
>
> 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
(v8.3.4#803005)