Increase KUBE_TIMEOUT from 60s to 300s in .travis.yml. Our passing coverage runs

take 30-60s, but a number of them reach the 60s timeout and are aborted. It seems our Travis (and Shippable?) flakiness is self-inflicted due to too-short timeouts?

Increase KUBE_TIMEOUT from 60s to 300s in .travis.yml. Our passing coverage runs
389bf559 · Alex Mohr · 56bdd949 · 389bf559
Commit 389bf559 authored Mar 09, 2015 by Alex Mohr
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

.travis.yml .travis.yml +1 -1

No files found.
--- a/.travis.yml
+++ b/.travis.yml
@@ -15,7 +15,7 @@ install:
  - ./hack/build-go.sh

 script:
-  - KUBE_RACE="-race" KUBE_COVER="y" KUBE_GOVERALLS_BIN="$HOME/gopath/bin/goveralls" KUBE_TIMEOUT='-timeout 60s' KUBE_COVERPROCS=8 ./hack/test-go.sh -- -p=2
+  - KUBE_RACE="-race" KUBE_COVER="y" KUBE_GOVERALLS_BIN="$HOME/gopath/bin/goveralls" KUBE_TIMEOUT='-timeout 300s' KUBE_COVERPROCS=8 ./hack/test-go.sh -- -p=2
  - PATH=$HOME/gopath/bin:./third_party/etcd:$PATH ./hack/test-cmd.sh
  - PATH=$HOME/gopath/bin:./third_party/etcd:$PATH ./hack/verify-gendocs.sh
  - PATH=$HOME/gopath/bin:./third_party/etcd:$PATH ./hack/test-integration.sh