-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
skip the reason check for OOM reason test if it will fail #120460
skip the reason check for OOM reason test if it will fail #120460
Conversation
Related to #119600 |
/cc pacoxu |
774e732
to
75017e2
Compare
/retest |
Discussing a SIG Node CI meeting. This will fail on CRI-O as well. SO we may be better off by skipping the test altogether. |
Link from @haircommander: opencontainers/runc#3932 |
another xref cri-o/cri-o#7035 |
This is currently flaking badly due to a race between cgroup deletion and the runtime detecting the OOM kill.
75017e2
to
94afd6e
Compare
/priority important-soon |
IIRC, can we add |
I could be convinced either way, but I prefer this method as it still tests that the termination occurs for the single & multi-process cases and just skips the flaking bit instead of the entire test. |
Opened up #121031 to help resolve these failures. |
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
LGTM label has been added. Git tree hash: a7fffa16fb4e562956ce97366341b49fa3767b1c
|
/assign @SergeyKanzhelev |
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: SergeyKanzhelev, tzneal 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 |
What type of PR is this?
/kind flake
What this PR does / why we need it:
This is currently flaking for both containerd/crio due to a race in cgroup deletion and reading the memory.events file were the OOMKill is recorded. Skip the part that fails for now until the issue is resolved.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: