Promote job completion after failure e2e test to Conformance

This commit is contained in:
Aaron Crickenberger 2019-07-24 17:17:07 -07:00
parent acd597dbac
commit e0b9d77609
2 changed files with 8 additions and 2 deletions

View File

@ -25,6 +25,7 @@ test/e2e/apps/deployment.go: "RecreateDeployment should delete old pods and crea
test/e2e/apps/deployment.go: "deployment should delete old replica sets"
test/e2e/apps/deployment.go: "deployment should support rollover"
test/e2e/apps/deployment.go: "deployment should support proportional scaling"
test/e2e/apps/job.go: "should run a job to completion when tasks sometimes fail and are locally restarted"
test/e2e/apps/job.go: "should delete a job"
test/e2e/apps/rc.go: "should serve a basic image on each replica with a public image"
test/e2e/apps/rc.go: "should surface a failure condition on a common issue like exceeded quota"

View File

@ -83,8 +83,13 @@ var _ = SIGDescribe("Job", func() {
framework.ExpectNoError(err, "failed to get PodList for job %s in namespace: %s", job.Name, f.Namespace.Name)
})
// Pods sometimes fail, but eventually succeed.
ginkgo.It("should run a job to completion when tasks sometimes fail and are locally restarted", func() {
/*
Release : v1.16
Testname: Jobs, completion after task failure
Description: Explicitly cause the tasks to fail once initially. After restarting, the Job MUST
execute to completion.
*/
framework.ConformanceIt("should run a job to completion when tasks sometimes fail and are locally restarted", func() {
ginkgo.By("Creating a job")
// One failure, then a success, local restarts.
// We can't use the random failure approach used by the