github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
96,061 Commits 1 Branch 31 Tags 1,019 MiB
acb43c7c4a
Commit Graph

46 Commits

Author SHA1 Message Date
yodarshafrir1
24010022ef Number of failed jobs should exceed the backoff limit and not big equal. 
Remove patch in e2e test of backoff limit due to usage of NumRequeues
 2020-08-11 11:06:09 +03:00
Jefftree
ace97738e2 Update formatting of conformance comment 2020-07-29 20:50:44 -07:00
drfish
f4da086cbe Move resource methods from e2e fw to e2e resource fw 2020-03-08 15:27:49 +08:00
Mike Danese
3aa59f7f30 generated: run refactor 2020-02-07 18:16:47 -08:00
toyoda
0c12ae5240 Modify alias of e2e/framework/job to e2ejob 2020-01-17 10:56:05 +09:00
Kubernetes Prow Robot
9d1eb45bc6
Merge pull request #86627 from tnqn/flaky-e2e-job 
Fix a flaky e2e test of Job completion
 2020-01-11 02:43:36 -08:00
Quan Tian
c84a371f3d Fix a flaky e2e test of Job completion 
The test was flaky because it required the job succeeds 3 times with
pseudorandom 50% failure chance within 15 minutes, while there is an
exponential back-off delay (10s, 20s, 40s …) capped at 6 minutes before
recreating failed pods. As 7 consecutive failures (1/128 chance) could
take 20+ minutes, exceeding the timeout, the test failed intermittently
because of "timed out waiting for the condition".

This PR forces the Pods of a Job to be scheduled to a single node and
uses a hostPath volume instead of an emptyDir to persist data across new
Pods.
 2020-01-10 16:04:56 +08:00
Kubernetes Prow Robot
de3be348a6
Merge pull request #86640 from tanjunchen/move-code-test/e2e/framework/job 
move funcs from test/e2e/framework/job to test/e2e/apps
 2019-12-27 19:47:51 -08:00
tanjunchen
794a8668fa move funcs from test/e2e/framework/job to test/e2e/apps 2019-12-27 09:35:30 +08:00
danielqsj
6596a14d39 add missing alias of api errors under test 2019-12-26 17:29:38 +08:00
tanjunchen
f786cb07b7 test/e2e/: use framework.Equal() replace gomega.Expect(...).To(gomega.BeTrue()|BeFalse()) 2019-12-13 10:11:47 +08:00
Benjamin Elder
4967f74599 check that N job pods succceeded instead of exactly N pods existing and succeeding 2019-10-03 11:03:44 -07:00
toyoda
c3fdb5e7d9 Use log functions of core framework on test/e2e/apps 2019-08-26 17:38:11 +09:00
Kubernetes Prow Robot
9e4b126e18
Merge pull request #80550 from spiffxp/promote-jobs-complete-after-restart 
Promote job completion after failure e2e test to Conformance
 2019-07-25 22:35:58 -07:00
Aaron Crickenberger
e0b9d77609 Promote job completion after failure e2e test to Conformance 2019-07-24 17:17:07 -07:00
Aaron Crickenberger
275b7b2fa0 Promote job pod orphaning/adotion e2e test to Conformance 2019-07-24 16:28:10 -07:00
Kubernetes Prow Robot
de9fb9c61c
Merge pull request #75632 from globervinodhn/correct_testname_backofflimit 
Correct test name for existing E2E related to backofflimit in jobs
 2019-07-19 12:37:11 -07:00
globervinodhn
c4e324196f correct testname for existing E2E for testing backoff limit for jobs 2019-07-17 21:46:31 +05:30
globervinodhn
7c8b81a30b correct testname for E2E related to active deadline in jobs 2019-07-17 21:42:52 +05:30
tanshanshan
2c130b236c Use ExpectEqual under apps 2019-07-04 08:43:42 +08:00
Kubernetes Prow Robot
ce2836831f
Merge pull request #76315 from globervinodhn/new_e2e_removejobpods 
New E2E proposal: Validate that all the pods are removed when the job is deleted
 2019-07-01 12:53:21 -07:00
SataQiu
332be4b1e3 refactor: replace framework.Failf with e2elog.Failf 2019-06-19 17:52:35 +08:00
globervinodhn
86f13ecb5a New E2E to verify pods are deleted after Job deletion 2019-06-06 10:42:48 +05:30
Jorge Alarcon Ochoa
4969a05327 Refactored pod-related functions from framework/util.go 
This a refactoring of framework/utils.go into framework/pod.

Signed-off-by: Jorge Alarcon Ochoa <alarcj137@gmail.com>
 2019-05-30 09:30:26 -04:00
toyoda
7acb1540a9 Use framework.ExpectError() for e2e/a* 2019-05-24 15:16:02 +09:00
toyoda
8afecb8c30 add pod status check after job completes in job e2e test 2019-05-07 11:47:56 +09:00
toyoda
2c098b37e3 use framework.ExpectNoError() for e2e/apps 2019-04-26 19:23:12 +09:00
SataQiu
03180ec2b2 fix golint failures of test/e2e/apps 2019-04-17 19:04:51 +08:00
Kubernetes Prow Robot
c3ac9fb1ab
Merge pull request #74791 from globervinodhn/job_delete_promote 
Promote graceful job deletion e2e test to conformance test
 2019-04-12 14:29:53 -07:00
draveness
f32352ac7e refactor: clean up e2e framework job utils 
1. Move job_util to e2e/framework/job package
2. Remove unused UpdateJobWithFunc
 2019-04-12 21:26:33 +08:00
globervinodhn
c52a27f409 promote job deletion in the namespace e2e to conformance - version updated to v1.15 2019-03-12 12:44:59 +05:30
ajatprabha
c3bc60b214 update error message 2019-01-25 13:29:43 +05:30
ajatprabha
e08f4e2bd2 annotate errors in apps/job e2e tests 2019-01-25 13:29:42 +05:30
Janet Kuo
0a6389e872 Add e2e test for TTL after finished 2018-09-04 14:21:14 -07:00
Maciej Szulik
d80ed537e5
Rate limit only when an actual error happens, not on update conflicts 2018-06-05 22:53:09 +02:00
Janet Kuo
de622012a6
Test job backoffLimit correctly 2018-06-05 00:47:46 +02:00
Maciej Szulik
383872615d
Remove kubectl reapers 2018-05-25 22:18:05 +02:00
p0lyn0mial
1f1d24005a removes custom scalers from kubectl 2018-03-26 19:33:42 +02:00
Maciej Szulik
90e7b5ff4f
Decrease the number of completions for flaky test 2017-12-07 16:05:35 +01:00
Maciej Szulik
9991a88870
Increase backoffLimit for job that we expect to fail several times 2017-10-03 13:45:41 +02:00
cedric lamoriniere
0d7182f8bd 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.
 2017-09-14 11:08:48 +02:00
cedric lamoriniere
1dbef2f113
Job failure policy support in JobController 
Job failure policy integration in JobController. From the
JobSpec.BackoffLimit the JobController will define the backoff
duration between Job retry.

It use the ```workqueue.RateLimitingInterface``` to store the number of
"retry" as "requeue" and the default Job backoff initial duration is set
during the initialization of the ```workqueue.RateLimiter.

Since the number of retry for each job is store in a local structure
"JobController.queue" if the JobController restarts the number of retries
will be lost and the backoff duration will be reset to 0.

Add e2e test for Job backoff failure policy
 2017-09-03 12:07:12 +02:00
Kubernetes Submit Queue
25da6e64e2 Merge pull request #48454 from weiwei04/check-job-activeDeadlineSeconds 
Automatic merge from submit-queue (batch tested with PRs 44719, 48454)

check job ActiveDeadlineSeconds

**What this PR does / why we need it**:

enqueue a sync task after ActiveDeadlineSeconds

**Which issue this PR fixes** *: 

fixes #32149

**Special notes for your reviewer**:

**Release note**:

```release-note
enqueue a sync task to wake up jobcontroller to check job ActiveDeadlineSeconds in time
```
 2017-08-29 08:25:06 -07:00
Wei Wei
46239ea30b check job ActiveDeadlineSeconds 2017-08-29 20:15:11 +08:00
Mikhail Mazurskiy
b28a83a4cf
Migrate to GetControllerOf from meta/v1 package 2017-08-06 22:41:58 +10:00
Michail Kargakis
5e93ed27bd
Rename test dir to allude sig-apps ownership 
Signed-off-by: Michail Kargakis <mkargaki@redhat.com>
 2017-07-22 12:43:36 +02:00