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
failed_when lists are implicitely ANDs, not ORs #6815
failed_when lists are implicitely ANDs, not ORs #6815
Conversation
1281ac2
to
9660194
Compare
Sorry, I thought that was intentional in the original PR. I imagine just checking for rc != 0 is sufficient to cover all cases but this minimizes additional change. |
Flakes /retest |
/test install |
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
Flakes |
flakes /retest |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. |
@vrutkovs: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
For some reason I believed
failed_when
lists are considered to be ORs, but it turns out these are ANDs.Fixes bug 1534538
Relates to #6751