-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Bug 1845434: router/grpc-interop: switch to WaitForPodRunningSlow #25082
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
Conversation
|
@frobware: This pull request references Bugzilla bug 1845434, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
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/test-infra repository. |
|
/assign @knobunc |
|
/retest |
|
@openshift/openshift-team-network-edge |
|
@frobware will this be cherry picked to 4.5? I see the test failing in our 4.2->4.5 upgrade testing: |
|
i'm going to proactively clone the BZ to 4.5 to ensure it gets discussed for backport |
|
/test e2e-aws-fips |
Thanks. I wanted to see this pass a couple of times before making that call. I'm pretty sure 15m should be enough. |
|
/retest |
The builder pod is taking a long time to complete in CI. In local testing (i.e., on a quiescent cluster) it takes between 45s-60s to complete. In CI this is taking much longer so switching to WaitForPodRunningSlow which has a longer timeout (currently 15m). To help reduce flakes: - Increase internal test timeout to 5m - Reduce number of test iterations from 5 to 2. We want to run more than once but 5 is probably unnecessary in CI so now reducing to just 2 iterations. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1845434
|
/retest |
1 similar comment
|
/retest |
|
@frobware: This pull request references Bugzilla bug 1845434, which is valid. 3 validation(s) were run on this bug
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/test-infra repository. |
|
@frobware: This pull request references Bugzilla bug 1845646, which is invalid:
Comment 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/test-infra repository. |
|
/refresh title |
|
/bugzilla refresh |
|
@frobware: This pull request references Bugzilla bug 1845646, which is invalid:
Comment 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/test-infra repository. |
|
@frobware: This pull request references Bugzilla bug 1845434, which is valid. 3 validation(s) were run on this bug
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/test-infra repository. |
|
/retest |
|
/test e2e-aws-fips |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: frobware, knobunc 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 |
|
/cherry-pick release-4.5 |
|
@frobware: once the present PR merges, I will cherry-pick it on top of release-4.5 in a new PR and assign it to you. 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/test-infra repository. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
7 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@frobware: All pull requests linked via external trackers have merged: openshift/origin#25082. Bugzilla bug 1845434 has been moved to the MODIFIED state. 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/test-infra repository. |
|
@frobware: new pull request created: #25104 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/test-infra repository. |
The builder pod is taking a long time to complete in CI. In local
testing (i.e., on a quiescent cluster) it takes between 45s-60s to
complete. In CI this is taking much longer so switching to
WaitForPodRunningSlow which has a longer timeout (currently 15m).
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1845434
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1845646