Skip to content

K
k3s
Commit 4181422a authored by Peter Hornyack's avatar Peter Hornyack
Browse files
Options

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.
parent e476ab63
Hide whitespace changes
Inline Side-by-side
Showing with 1 addition and 1 deletion
cluster/gce/windows/smoke-test.sh
View file @ 4181422a
...@@ -40,7 +40,7 @@ ...@@ -40,7 +40,7 @@
# Override this to use a different kubectl binary. # Override this to use a different kubectl binary.
kubectl=kubectl kubectl=kubectl
linux_deployment_timeout=60 linux_deployment_timeout=60
windows_deployment_timeout=120 windows_deployment_timeout=180
output_file=/tmp/k8s-smoke-test.out output_file=/tmp/k8s-smoke-test.out
function check_windows_nodes_are_ready { function check_windows_nodes_are_ready {
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment