From 512a4e8a3e2e0762537fd2be8a2df48492fb1b2e Mon Sep 17 00:00:00 2001 From: Francesco Romani Date: Mon, 10 Feb 2020 16:35:14 +0100 Subject: [PATCH] e2e: topomgr: reduce node readiness timeout Five minutes was initially used only to be overcautious. From my experiments, the node is ready in usually less than a minute. Double it to give some buffer space. Signed-off-by: Francesco Romani --- test/e2e_node/topology_manager_test.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/e2e_node/topology_manager_test.go b/test/e2e_node/topology_manager_test.go index bd6a8b314cb..6d5882ce86e 100644 --- a/test/e2e_node/topology_manager_test.go +++ b/test/e2e_node/topology_manager_test.go @@ -626,7 +626,7 @@ func runTopologyManagerNodeAlignmentSuiteTests(f *framework.Framework, configMap framework.Logf("Node status: %v", node.Status.Capacity) sriovResourceName, sriovResourceAmount = findSRIOVResource(node) return sriovResourceAmount > 0 - }, 5*time.Minute, framework.Poll).Should(gomega.BeTrue()) + }, 2*time.Minute, framework.Poll).Should(gomega.BeTrue()) framework.Logf("Successfully created device plugin pod, detected %d SRIOV device %q", sriovResourceAmount, sriovResourceName) threadsPerCore := 1