-
Couldn't load subscription status.
- Fork 1.1k
test: Test for OOM condition in a loop #1055
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
Conversation
|
/test all |
bbf3df8 to
4658391
Compare
|
/test integration_rhel |
|
oom is still failing. :^( |
|
It passed in #1054 |
|
/test integration_rhel |
|
With happy tests, LGTM |
|
@stevekuznetsov Did we by any chance either change the base of RHEL ami or change the type of instances that we run the tests on? Reason for asking is that OOM test is not completing in even 10 minutes when it used to 100 seconds last tim e we bumped up the timeout for it. |
|
The size of the instances has not changed. The AMI jobs are here: https://ci.openshift.redhat.com/jenkins/job/ami_build_origin_int_rhel_crio/ Can you constrain how much memory is available using |
|
Is this problem caused by the swap patch that @cevich added? And we are just swapping? |
|
@rhatdan Let me look into that. That could explain this. |
Signed-off-by: Mrunal Patel <[email protected]>
4658391 to
17db40d
Compare
|
/test all |
|
/test integration_rhel |
Signed-off-by: Mrunal Patel [email protected]