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
USHIFT-3143: Skip metrics and adjust termination message policy monitor tests #28787
Conversation
@pacevedom: This pull request references USHIFT-3143 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
/cc @dgoodwin |
/retest-required |
/hold |
/hold cancel |
/lgtm We need to get a presubmit for microshift in here soon. |
/hold |
/cc @dgoodwin ptal again, I changed one of the tests to allow it to work on MicroShift. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dgoodwin, pacevedom 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 |
/hold cancel |
/retest-required |
1 similar comment
/retest-required |
/retest-required |
2 similar comments
/retest-required |
/retest-required |
I'm not totally sure what's happening here but I fear your presubmits are stuck running code that was reverted last week. Those panics should have been resolved, and I don't see them firing anywhere else. We've seen this before where PRs get "stuck" on old code and have to be reopened as a new PR. Honestly I think that's what I'd recommend at this point. |
Job Failure Risk Analysis for sha: cb99e59
|
/retest-required |
MicroShift does not support metrics server yet. It is unclear how it will do when it does, so for now skip this test.
MicroShift does not support ClusterVersion resources, but this test only uses it to determine if there were past versions that could skip the checks due to older versions. Since there is no notion of past knowledge in MicroShift, adjust the test to not require ClusterVersion.
New changes are detected. LGTM label has been removed. |
@pacevedom: 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-sigs/prow repository. I understand the commands that are listed here. |
MicroShift does not support metrics server yet. It is unclear how it will do when it does, so for now skip this test.