[kudu-CR] Fixes for flaky-test build

["Todd Lipcon (Code Review)" <ge...@cloudera.org>]

Hello Adar Dembo,

I'd like you to do a code review.  Please visit

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

to review the following change.

Change subject: Fixes for flaky-test build
......................................................................

Fixes for flaky-test build

The RUN_FLAKY_ONLY build rotted a bit, and we didn't notice because we don't
get notified when the flaky test build fails (we expect it to fail basically
all the time since it only runs flaky tests.) It also rotted in such a way that
it ran _all_ the tests, so we were still seeing useful data on the dashboard.

- Fetch the test list into the proper build dir
- Report a better error and exit immediately if the flaky test server is down
- Exit the script early if there are no flaky tests
- Disable the python build since we don't do flaky-tracking for python.

Change-Id: Id6b284e9643fc336e3dbd6a997f0bd60759e97cd
---
M build-support/jenkins/build-and-test.sh
1 file changed, 16 insertions(+), 5 deletions(-)


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

Gerrit-MessageType: newchange
Gerrit-Change-Id: Id6b284e9643fc336e3dbd6a997f0bd60759e97cd
Gerrit-PatchSet: 1
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Todd Lipcon <to...@apache.org>
Gerrit-Reviewer: Adar Dembo <ad...@cloudera.com>