From 0d7182f8bd64a194e7aace094b11c8390ee2d5ce Mon Sep 17 00:00:00 2001 From: cedric lamoriniere Date: Thu, 14 Sep 2017 11:08:48 +0200 Subject: [PATCH] Fix e2e Flaky Apps/Job BackoffLimit test This fix is linked to the PR #51153 that introduce the JobSpec.BackoffLimit. Previously the Timeout used in the test was too agressive and generates flaky test execution. Now it used the default framework.JobTimeout used in others tests. --- test/e2e/apps/job.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/e2e/apps/job.go b/test/e2e/apps/job.go index 608106d6db4..c1573557816 100644 --- a/test/e2e/apps/job.go +++ b/test/e2e/apps/job.go @@ -181,7 +181,7 @@ var _ = SIGDescribe("Job", func() { Expect(err).NotTo(HaveOccurred()) By("Ensuring job exceed backofflimit") - err = framework.WaitForJobFailure(f.ClientSet, f.Namespace.Name, job.Name, time.Duration(30)*time.Second, "BackoffLimitExceeded") + err = framework.WaitForJobFailure(f.ClientSet, f.Namespace.Name, job.Name, framework.JobTimeout, "BackoffLimitExceeded") Expect(err).NotTo(HaveOccurred()) By("Checking that only one pod created and status is failed")