From 4181422a3ce1be0f8e304151c81d220c5d79d785 Mon Sep 17 00:00:00 2001 From: Peter Hornyack Date: Thu, 28 Feb 2019 14:22:33 -0800 Subject: [PATCH] Increase Windows smoke-test timeout to 3 minutes. I recently lowered the timeout value to 2 minutes but this turned out to be too aggressive for now. 3 minutes is usually long enough for the test containers to come up. Note that this test is only used during development, it does not run continuously anywhere. --- cluster/gce/windows/smoke-test.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cluster/gce/windows/smoke-test.sh b/cluster/gce/windows/smoke-test.sh index 3b4079f852..f820eb5a4d 100755 --- a/cluster/gce/windows/smoke-test.sh +++ b/cluster/gce/windows/smoke-test.sh @@ -40,7 +40,7 @@ # Override this to use a different kubectl binary. kubectl=kubectl linux_deployment_timeout=60 -windows_deployment_timeout=120 +windows_deployment_timeout=180 output_file=/tmp/k8s-smoke-test.out function check_windows_nodes_are_ready {