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
[release-4.5] Bug 1845291: Measure container restarts over an interval instead of absolute #25152
[release-4.5] Bug 1845291: Measure container restarts over an interval instead of absolute #25152
Conversation
We run these tests after disruptive events where restarts are necessary. Instead of looking at absolute restart count, capture the number of initial restarts and then compare subsequent runs to ensure the count is smaller. We double the time interval and halve the number of failing restarts in order to ensure we capture slow restart failures (full backoff is 5m, but we can catch slow but not limited backoff).
/lgtm |
/test e2e-conformance-k8s |
/retest |
/refresh |
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hexfusion, mfojtik, openshift-cherrypick-robot 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 |
This needs an override on e2e-aws-disruptive as this patch helps fix the test. |
@openshift-cherrypick-robot: This pull request references Bugzilla bug 1845291, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. 6 validation(s) were run on this bug
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. |
@openshift-cherrypick-robot: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
Force merging because the test itself passed and we need to unblock the disurptive suite |
@openshift-cherrypick-robot: Some pull requests linked via external trackers have merged: openshift/origin#25152. The following pull requests linked via external trackers have not merged:
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. |
This is an automated cherry-pick of #25115
/assign hexfusion