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
Bug 1957295: test/extended/pods/priorityclasses: Improve error actionability #26174
Bug 1957295: test/extended/pods/priorityclasses: Improve error actionability #26174
Conversation
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 for working on this @wking
/lgtm
566baa6
to
f059372
Compare
f059372
to
e5d8801
Compare
Instead of just telling folks which pods are broken, tell folks what the current config is and what the expected config is, so they don't have to dig around to figure out how to fix their component. Also switch from Contains to HasPrefix, because as pointed out in d6c4a51 (Components should have required Priorityclass, 2021-05-02, openshift#25931), we're looking for openshift-user-critical, system-cluster-critical, or system-node-critical.
e5d8801
to
368a632
Compare
@wking: This pull request references Bugzilla bug 1957295, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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. |
@soltysh, you approved the earlier PR; can you review this follow-up? |
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ravisantoshgudimetla, soltysh, wking 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 |
/retest Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@wking: The following tests failed, say
Full PR test history. Your PR dashboard. 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. |
@wking: All pull requests linked via external trackers have merged: Bugzilla bug 1957295 has been moved to the MODIFIED state. In response to this:
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. |
Instead of just telling folks which pods are broken, tell folks what the current config is and what the expected config is, so they don't have to dig around to figure out how to fix their component.
Following up on d6c4a51 (#25931), CC @ravisantoshgudimetla.