CORENET-6168: remove two broken tests from the blocking list#3043
CORENET-6168: remove two broken tests from the blocking list#3043jluhrsen wants to merge 1 commit into
Conversation
|
@jluhrsen: This pull request references CORENET-6168 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 story to target the "4.22.0" version, but no target version was set. DetailsIn 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. |
|
/test e2e-aws-ovn-edge-zones |
|
/retest-required @jcaamano can you override any failed tests here. this PR is removing two test cases from the list of blocking cases and has nothing to do with any e2e job failures. /hold /verified by jamo |
|
@jluhrsen: This PR has been marked as verified by DetailsIn 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. |
|
/test e2e-metal-ipi-ovn-dualstack-bgp |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jcaamano, jluhrsen The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/override ci/prow/qe-perfscale-payload-control-plane-6nodes |
|
@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/qe-perfscale-payload-control-plane-6nodes DetailsIn 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-sigs/prow repository. |
|
/override ci/prow/e2e-metal-ipi-ovn-dualstack |
|
@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/e2e-metal-ipi-ovn-dualstack, ci/prow/e2e-metal-ipi-ovn-dualstack-bgp, ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw DetailsIn 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-sigs/prow repository. |
|
/hold cancel |
|
/hold |
|
@jluhrsen it looks like we may also skip running IPv6 tests as well. can you take a look ? |
I think we need this upstream PR to solve this one. I didn't push on it hard enough yet I guess. will try to get it moved along. |
the k8s bump to 1.35 has changed the error format [0] these test cases are expecting so these cases will fail until the fix upstream [1] is merged and makes it downstream. after that we can revert this commit so they will be blocking again [0] kubernetes/kubernetes@a674687 [1] ovn-kubernetes/ovn-kubernetes#6077 Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
2faea6f to
9adab4d
Compare
|
New changes are detected. LGTM label has been removed. |
oh, I see what you mean. yes, I just updated this PR to exclude those. Let's get this thing merged asap please. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
WalkthroughFour Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@jluhrsen: This pull request references CORENET-6168 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 story to target the "4.22.0" version, but no target version was set. DetailsIn 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. |
|
/hold cancel |
|
/hold I don't understand why we are doing a downstream specific PR |
|
@jluhrsen: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
@tssurya , it was so that we can maybe finally hopefully turn OTE on so we can catch issues on d/s merge PRs if/when they come instead of finding them later and still not able to turn our OTE on. I have been in a waiting pattern for months to get the origin PR in because of one thing after another. yes, upstream needs to fix it. I had my own PR I asked to get in 3 weeks ago and didn't find traction. but now I see the So, I suppose now that the upstream rebase is in our next d/s merge will work? I guess we'll see. |
|
/close |
|
@jluhrsen: Closed this PR. DetailsIn 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-sigs/prow repository. |
the k8s bump to 1.35 has changed the error format [0] these test cases are expecting so these cases will fail until the fix upstream [1] is merged and makes it downstream. after that we can revert this commit so they will be blocking again
[0] kubernetes/kubernetes@a674687
[1] ovn-kubernetes/ovn-kubernetes#6077
📑 Description
Fixes #
Additional Information for reviewers
✅ Checks
How to verify it
Summary by CodeRabbit