-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(taskrun): resolve issue with TaskRun not failing promptly after Pod OOM #8171
Conversation
Hi @l-qing. Thanks for your PR. I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/ok-to-test
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest-required |
3 similar comments
/retest-required |
/retest-required |
/retest-required |
cc @tektoncd/core-maintainers |
876e529
to
46f6671
Compare
/lgtm |
/retest |
1 similar comment
/retest |
Thank you. I'll check the reason for this failure tomorrow. |
/retest-required |
…od OOM fix tektoncd#8170 When an OOM occurs in a Pod related to TaskRun, the TaskRun should be marked as failed immediately instead of waiting for it to timeout.
46f6671
to
0083168
Compare
The problem of sporadic failures regarding the e2e |
/retest-required |
/lgtm |
/retest-required |
fix #8170
When an OOM occurs in a Pod related to TaskRun, the TaskRun should be marked as failed immediately instead of waiting for it to timeout.
This issue has been present in several recent LTS versions, including v0.53, v0.56, v0.59, and v0.62
Changes
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes
/kind bug