From 77c04d22844c45774c98b0c36f3aad993f28a767 Mon Sep 17 00:00:00 2001 From: Benjamin Elder Date: Wed, 9 Jun 2021 23:33:24 -0700 Subject: [PATCH] Increase KUBE_TIMEOUT default to a passing default Next we can stop overriding it in CI, so local and CI runs match more closely, see: https://github.com/kubernetes/kubernetes/issues/102607 --- hack/make-rules/test.sh | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/hack/make-rules/test.sh b/hack/make-rules/test.sh index 7b8637a130f..06c354df3f8 100755 --- a/hack/make-rules/test.sh +++ b/hack/make-rules/test.sh @@ -59,7 +59,10 @@ kube::test::find_dirs() { ) } -KUBE_TIMEOUT=${KUBE_TIMEOUT:--timeout=120s} +# TODO: This timeout should really be lower, this is a *long* time to test one +# package, however pkg/api/testing in particular will fail with a lower timeout +# currently. We should attempt to lower this over time. +KUBE_TIMEOUT=${KUBE_TIMEOUT:--timeout=170s} KUBE_COVER=${KUBE_COVER:-n} # set to 'y' to enable coverage collection KUBE_COVERMODE=${KUBE_COVERMODE:-atomic} # The directory to save test coverage reports to, if generating them. If unset,