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 <[email protected]>
gavinxub · Feb 10, 2020 · 512a4e8 · 512a4e8
1 parent 3b4122b
commit 512a4e8
Showing 1 changed file with 1 addition and 1 deletion.
diff --git 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