Hello Kudu Jenkins, Adar Dembo, Todd Lipcon,

I'd like you to reexamine a change. Please visit

    http://gerrit.cloudera.org:8080/11374

to look at the new patch set (#3).

Change subject: build: retry failed tests by default
......................................................................

build: retry failed tests by default

Previously, the option KUDU_FLAKY_TEST_ATTEMPTS, would either pull the
list of flaky tests from the test server and retry those tests, or retry
all flaky tests if specified by the user. This patch updates the unit
test run logic to retry all failed tests. Now, the flaky test list will
only be used to specify which tests to run, e.g. if RUN_FLAKY_ONLY is
set.

The new default when running build-and-test.sh without dist-test enabled
will be to retry 3 times for all failed tests. The default when running
with dist test enabled has been unchanged.

I tested this locally by running run-test.sh with a dummy failed test,
setting KUDU_FLAKY_TEST_ATTEMPTS to a couple different values.

Here are some dist test runs with KUDU_FLAKY_TEST_ATTEMPTS=2:
http://dist-test.cloudera.org/job?job_id=awong.1535756796.39753

One with KUDU_FLAKY_TEST_ATTEMPTS unset:
http://dist-test.cloudera.org/job?job_id=awong.1535756961.40518

Change-Id: I6fc069527d6f2553a4e04e14c821090f826cbc0a
---
M build-support/dist_test.py
M build-support/jenkins/build-and-test.sh
M build-support/run-test.sh
3 files changed, 15 insertions(+), 76 deletions(-)


  git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/74/11374/3
--
To view, visit http://gerrit.cloudera.org:8080/11374
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-MessageType: newpatchset
Gerrit-Change-Id: I6fc069527d6f2553a4e04e14c821090f826cbc0a
Gerrit-Change-Number: 11374
Gerrit-PatchSet: 3
Gerrit-Owner: Andrew Wong <[email protected]>
Gerrit-Reviewer: Adar Dembo <[email protected]>
Gerrit-Reviewer: Andrew Wong <[email protected]>
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Todd Lipcon <[email protected]>

Reply via email to