-
Notifications
You must be signed in to change notification settings - Fork 14
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 e2e OOM tests #944
🧹 Add e2e OOM tests #944
Conversation
4a21d0c
to
26c717c
Compare
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.
Thank you @czunker
Finally, I found out why these tests are failing. We have a bug in the CronJob Schedule that makes these tests fail. The schedule for the k8s resource scan is constantly changed and this changes the number of expected objects in these tests. I assume we have the actual bug from the beginning of the CronJobs, but exposed it with #938. Need to find a fix for the schedule, before we can merge this PR. |
When tests pass for #948 and it is merged, this needs a rebase for tests to also succeed here. |
This adds e2e tests for OOM of Scan API and node scan. This covers the two different cases we currently have: Deployment and CronJob. Fixes #940 Signed-off-by: Christian Zunker <[email protected]>
Signed-off-by: Christian Zunker <[email protected]>
Signed-off-by: Christian Zunker <[email protected]>
a3dcea7
to
ccbe3ed
Compare
Signed-off-by: Christian Zunker <[email protected]>
ccbe3ed
to
03339a9
Compare
This adds e2e tests for OOM of Scan API and node scan. This covers the two different cases we currently have: Deployment and CronJob.
Fixes #940