-
Notifications
You must be signed in to change notification settings - Fork 24
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 cleanup logging after tests run #246
Add cleanup logging after tests run #246
Conversation
We've noticed that some of the tests aren't cleaning up the way we expect. Specifically, some of the compliance scans are still laying around even when we exit the context Cleanup() function, which is designed to execute a bunch of callbacks to cleanup test resources. This probably isn't much of a problem in CI since the cluster gets torn down after the tests run, but it impacts contributor's ability to re-use the same environment for multiple e2e runs. Ideally, we want to run a single test in isolation and have it cleanup after itself so we can continue using the same environment. This commit adds basic logging in Cleanup() that logs how many scans are left over before we tear down the environment.
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: rhmdnd, Vincent056 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 |
Looks like the issue is in CI, too:
|
adding the labels that prow wants |
We've noticed that some of the tests aren't cleaning up the way we
expect. Specifically, some of the compliance scans are still laying
around even when we exit the context Cleanup() function, which is
designed to execute a bunch of callbacks to cleanup test resources.
This probably isn't much of a problem in CI since the cluster gets torn
down after the tests run, but it impacts contributor's ability to re-use
the same environment for multiple e2e runs. Ideally, we want to run a
single test in isolation and have it cleanup after itself so we can
continue using the same environment.
This commit adds basic logging in Cleanup() that logs how many scans are
left over before we tear down the environment.