From f0211a8860af98d9aa20aac393b817c9bb397242 Mon Sep 17 00:00:00 2001 From: Hidde Beydals Date: Fri, 8 Dec 2023 18:13:26 +0100 Subject: [PATCH] ci: increase timeout delete-ns tests This test has shown to be a flake on multiple ocassions. After running it locally a dozen of times, my conclusion is that the time it takes for Kubernetes to shutdown a Pod may sometimes take a tiny bit longer than anticipated by the current timeout. Therefore, increase it to 5 minutes and provide more context on the state of the namespace in case a timeout occurs. Signed-off-by: Hidde Beydals --- .github/workflows/e2e.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/e2e.yaml b/.github/workflows/e2e.yaml index 4d5e961c4..e4d2f8084 100644 --- a/.github/workflows/e2e.yaml +++ b/.github/workflows/e2e.yaml @@ -538,10 +538,11 @@ jobs: kubectl -n delete-ns wait helmreleases/podinfo --for=condition=ready --timeout=2m kubectl delete ns delete-ns 1>/dev/null 2>&1 & echo -n ">>> Waiting for namespace to be deleted" - if kubectl wait --for=delete namespace delete-ns --timeout=3m; then + if kubectl wait --for=delete namespace delete-ns --timeout=5m; then echo ' Namespace deleted successfully' else echo ' Timed out waiting for namespace to be deleted' + kubectl get all -n delete-ns exit 1 fi - name: Run post-renderer-kustomize test