-
Notifications
You must be signed in to change notification settings - Fork 112
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
OCPBUGS-42087: storage/cacher/ready: dynamically calculate the retryAfterSeconds #2225
base: master
Are you sure you want to change the base?
OCPBUGS-42087: storage/cacher/ready: dynamically calculate the retryAfterSeconds #2225
Conversation
@bertinatto: This pull request references Jira Issue OCPBUGS-44693, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
@bertinatto: the contents of this pull request could not be automatically validated. The following commits are valid:
The following commits could not be validated and must be approved by a top-level approver:
Comment |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bertinatto 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 |
…ryAfterSeconds retryAfterSeconds is based on the time elapsed since the state (ready, unready) was last changed.
…eature" This reverts commit 4772890.
7f51183
to
5dc7dcb
Compare
@bertinatto: the contents of this pull request could not be automatically validated. The following commits are valid:
The following commits could not be validated and must be approved by a top-level approver:
Comment |
@bertinatto: This pull request references Jira Issue OCPBUGS-42087, which is invalid:
Comment 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. |
@bertinatto: the contents of this pull request could not be automatically validated. The following commits are valid:
The following commits could not be validated and must be approved by a top-level approver:
Comment |
@bertinatto: 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. |
Check if this patch improves the signal from /payload-aggregate periodic-ci-openshift-release-master-ci-4.19-e2e-aws-upgrade-ovn-single-node 10 |
@bertinatto: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/92dd9600-f61b-11ef-87c3-a6c13f832ae5-0 |
/payload 4.19 nightly blocking |
@bertinatto: trigger 12 job(s) of type blocking for the nightly release of OCP 4.19
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/916ba040-f7ac-11ef-9a4a-74b651ba4297-0 trigger 65 job(s) of type informing for the nightly release of OCP 4.19
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/916ba040-f7ac-11ef-9a4a-74b651ba4297-1 |
No description provided.