CI passes even when it actually timed out
- Dominant language
- Go
- Stars
- 1.6k
- Forks
- 617
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 43
Description
# Describe the bug #
CI passes even when it actually timed out
Example:
https://jenkins-ceph-csi.apps.ocp.ci.centos.org/blue/organizations/jenkins/mini-e2e-helm_k8s-1.23/detail/mini-e2e-helm_k8s-1.23/76/pipeline/99
https://jenkins-ceph-csi.apps.ocp.ci.centos.org/blue/organizations/jenkins/mini-e2e_k8s-1.22/detail/mini-e2e_k8s-1.22/1470/pipeline/93
https://jenkins-ceph-csi.apps.ocp.ci.centos.org/blue/organizations/jenkins/mini-e2e_k8s-1.23/detail/mini-e2e_k8s-1.23/77/pipeline/93
Especially on #2359 , since it add multiple e2e test cases which take more time.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inspecting the three linked Jenkins pipeline runs and the CI/e2e timeout handling related to issue #2359. Determine why timed-out jobs are reported as successful; done means reproducing the behavior and ensuring such runs are reported as failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100