-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
e2e test cleanup: check exit statuses #11597
Conversation
The e2e Cleanup handlers run various 'rm' commands, but don't check the exit status of any. This masks real problems such as the unlinkat-EBUSY flake (containers#11594) which only triggers on container/pod rm. Solution: check exit status: a failure in cleanup will now be considered a failure in the test itself. Signed-off-by: Ed Santiago <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: edsantiago 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 |
LGTM |
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 |
That's the point. The flakes are happening, we're just not seeing them. I'd rather see them here than downstream. |
Oh well. It was worth a shot. |
The e2e Cleanup handlers run various 'rm' commands, but don't
check the exit status of any. This masks real problems such
as the unlinkat-EBUSY flake (#11594) which only triggers on
container/pod rm.
Solution: check exit status: a failure in cleanup will now be
considered a failure in the test itself.
Signed-off-by: Ed Santiago [email protected]