Alexey Serbin has uploaded this change for review. ( 
http://gerrit.cloudera.org:8080/18947


Change subject: [tools] mark long-running scenarios in kudu-tool-test
......................................................................

[tools] mark long-running scenarios in kudu-tool-test

I noticed that it takes very long time for kudu-tool-test to complete.
It turned out the test suite contains many scenarios that run with
HMS integration enabled and it takes a long time to start up the
HMS process.

This patch marks the scenarios that tend to run over 3 seconds
as slow, so they are skipped unless the KUDU_ALLOW_SLOW_TESTS
environment variable is set to true/yes/1.

The run time of the kudu-tool-test with this patch looks like the
following on a contemporary Linux machine:

Without KUDU_ALLOW_SLOW_TESTS:
  [==========] 128 tests from 8 test suites ran. (86355 ms total)

With KUDU_ALLOW_SLOW_TESTS=1:
  [==========] 128 tests from 8 test suites ran. (842684 ms total)

Change-Id: I1893741fada185d819128396c88f4ac99f43ed40
---
M src/kudu/tools/kudu-tool-test.cc
1 file changed, 28 insertions(+), 3 deletions(-)



  git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/47/18947/1
--
To view, visit http://gerrit.cloudera.org:8080/18947
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-MessageType: newchange
Gerrit-Change-Id: I1893741fada185d819128396c88f4ac99f43ed40
Gerrit-Change-Number: 18947
Gerrit-PatchSet: 1
Gerrit-Owner: Alexey Serbin <[email protected]>

Reply via email to