mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-07-19 09:52:49 +00:00
tests: Set a 5 minute timeout for kubectl cluster-info dump
We've observed this test causing e2e runs to time-out; the ginkgo behaviour here is unhelpful, in that we don't see any output on a timeout. Set a (generous) time limit to start to get output and enforce some limit to the response time.
This commit is contained in:
parent
3d8dd2517f
commit
bc16100549
@ -1083,7 +1083,12 @@ metadata:
|
||||
ginkgo.Describe("Kubectl cluster-info dump", func() {
|
||||
ginkgo.It("should check if cluster-info dump succeeds", func() {
|
||||
ginkgo.By("running cluster-info dump")
|
||||
framework.RunKubectlOrDie(ns, "cluster-info", "dump")
|
||||
|
||||
// Should return in a timely fashion (or we should mark the test slow)
|
||||
timer := time.NewTimer(300 * time.Second)
|
||||
defer timer.Stop()
|
||||
|
||||
framework.NewKubectlCommand(ns, "cluster-info", "dump").WithTimeout(timer.C).ExecOrDie(ns)
|
||||
})
|
||||
})
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user