-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Add oomkilled reason #8709
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
Add oomkilled reason #8709
Conversation
/cc @aThorp96 |
@infernus01: GitHub didn't allow me to request PR reviews from the following users: aThorp96. Note that only tektoncd members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
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. |
/cc @PuneetPunamiya |
@infernus01: GitHub didn't allow me to request PR reviews from the following users: PuneetPunamiya. Note that only tektoncd members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
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. |
/kind bug |
/cc @waveywaves |
/ok-to-test |
/retest |
1 similar comment
/retest |
@infernus01 a bunch of tests are failing, if you could just check that would be great |
/retest |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
@@ -1468,7 +1468,7 @@ func TestMakeTaskRunStatus(t *testing.T) { | |||
}}, | |||
}, | |||
want: v1.TaskRunStatus{ | |||
Status: statusFailure(v1.TaskRunReasonFailed.String(), "\"step-one\" exited with code 137"), | |||
Status: statusFailure(v1.TaskRunReasonFailed.String(), "\"step-one\" exited with code 137: OOMKilled"), |
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.
Welp, this would explain why the CI was failing haha
The following is the coverage report on the affected files.
|
/retest |
/retest |
/lgtm |
@aThorp96: changing LGTM is restricted to collaborators In response to this:
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aThorp96, vdemeester, waveywaves 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 |
@infernus01 one thing I forgot to enforce here is the commit message standard, please remember to add proper commit messages in the next one |
Changes
This PR improves the error reporting for TaskRuns that fail due to Out of Memory (OOM) conditions. The changes modify the extractContainerFailureMessage function in pkg/pod/status.go to include the termination reason in the failure message when a container is OOMKilled.
Fix jira #SRVKP-7343
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind bug
.Release Notes