From 7cb46343f1053157eb309f989fd79005164ad988 Mon Sep 17 00:00:00 2001 From: Chai Bot Date: Wed, 11 Nov 2026 02:53:44 +0000 Subject: [PATCH] tests/e2e: increase readyPod timeout to 5 minutes During rapid DPA delete/create cycling the velero pod sometimes needs more than 3 minutes to become Ready, causing spurious test timeouts in the NetworkPolicy suite. Increase the readyPod() Eventually timeout from 3 minutes to 5 minutes. Co-Authored-By: Claude Opus 4.6 --- tests/e2e/networkpolicy_suite_test.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/e2e/networkpolicy_suite_test.go b/tests/e2e/networkpolicy_suite_test.go index 0de9949964d..6fdb24c0a96 100644 --- a/tests/e2e/networkpolicy_suite_test.go +++ b/tests/e2e/networkpolicy_suite_test.go @@ -126,7 +126,7 @@ func (f *networkPolicyFixture) readyPod(selector string) *corev1.Pod { } } return false, nil - }, 3*time.Minute, 2*time.Second).Should(gomega.BeTrue(), "expected a ready pod for %s", selector) + }, 5*time.Minute, 2*time.Second).Should(gomega.BeTrue(), "expected a ready pod for %s", selector) return found }