OCPBUGS-62132: Remove Expect func so that the test case can use the retry logic #665
Conversation
|
/test e2e-gcp-operator |
jianzhangbjz
force-pushed
the
fix
branch
2 times, most recently
from
2f2e982 to
c937b0b
Compare
jianzhangbjz
changed the title
|
/lgtm |
openshift-ci
bot
added
lgtm
|
@jianzhangbjz it needs a bug, especially if you want to backport this. |
|
The tests failed to get leases... |
|
The tests failed to get leases (again)... |
|
/retest-required |
jianzhangbjz
changed the title
openshift-ci-robot
added
jira/severity-moderate
|
@jianzhangbjz: This pull request references Jira Issue OCPBUGS-62132, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request. The bug has been updated to refer to the pull request using the external bug tracker. 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. |
|
/verified by e2e-gcp-operator |
|
@jianzhangbjz: This PR has been marked as verified by 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. |
|
Raise this failure issue to the DPTP team on Slack: https://redhat-internal.slack.com/archives/CBN38N3MW/p1758697723520629 |
|
/retest-required |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kevinrizza, perdasilva 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-required |
1 similar comment
|
/retest-required |
|
@jianzhangbjz: The following test 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. |
|
/retest-required |
|
/retest |
openshift-merge-bot
bot
merged commit 1b414bc
into
operator-framework:master
|
@jianzhangbjz: Jira Issue Verification Checks: Jira Issue OCPBUGS-62132 Jira Issue OCPBUGS-62132 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 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. |
|
/cherry-pick release-4.20 |
|
/cherry-pick release-4.19 |
|
/cherry-pick release-4.18 |
|
/cherry-pick release-4.17 |
|
/cherry-pick release-4.16 |
|
/cherry-pick release-4.15 |
|
/cherry-pick release-4.14 |
|
@jianzhangbjz: new pull request created: #667 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-sigs/prow repository. |
|
@jianzhangbjz: new pull request created: #668 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-sigs/prow repository. |
|
@jianzhangbjz: new pull request created: #669 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-sigs/prow repository. |
|
@jianzhangbjz: new pull request created: #670 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-sigs/prow repository. |
|
@jianzhangbjz: new pull request created: #671 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-sigs/prow repository. |
|
@jianzhangbjz: new pull request created: #672 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-sigs/prow repository. |
|
@jianzhangbjz: new pull request created: #673 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-sigs/prow repository. |
6 participants
Description of the change:
Increase default timeout.
Motivation for the change:
Try to fix #664 (comment)
Not only 4.16, but also the master, see: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/operator-framework_operator-marketplace/661/pull-ci-operator-framework-operator-marketplace-master-e2e-gcp-operator/1969926155641294848/artifacts/e2e-gcp-operator/test/build-log.txt
Reviewer Checklist
/docs