[incubator-openwhisk-deploy-kube] branch master updated: Increase timeout when trying to chown directory (#15)

[mr...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mrutkowski pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-openwhisk-deploy-kube.git


The following commit(s) were added to refs/heads/master by this push:
     new e7fd635  Increase timeout when trying to chown directory (#15)
e7fd635 is described below

commit e7fd635e8f8d1d08b69c5693f4309d5297605dbc
Author: Dan Lavine <dl...@us.ibm.com>
AuthorDate: Mon Jun 19 15:19:36 2017 -0500

    Increase timeout when trying to chown directory (#15)
    
    * Increase timout when trying to chown directory
    
    * Add comment for sleep command
---
 .travis/setup.sh | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/.travis/setup.sh b/.travis/setup.sh
index 1cc94eb..8f19f39 100755
--- a/.travis/setup.sh
+++ b/.travis/setup.sh
@@ -53,8 +53,14 @@ fi
 
 echo "Kubernetes is deployed and reachable"
 
+# Try and sleep before issuing chown. Currently, Kubernetes is started by
+# a command that is run in the background. Technically Kubernetes could be
+# up and running, but those files might not exist yet as the previous command
+# could create them after Kube starts successfully.
+sleep 1
+
 sudo chown -R $USER:$USER $HOME/.kube
 
 # Have seen issues where chown does not instantly change file permissions.
 # When this happens the build.sh cript can have failures.
-sleep 1
+sleep 30

-- 
To stop receiving notification emails like this one, please contact
['"commits@openwhisk.apache.org" <co...@openwhisk.apache.org>'].