-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Bug 1886160: Improve reliability of e2-aws-disruptive #25707
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
Bug 1886160: Improve reliability of e2-aws-disruptive #25707
Conversation
|
@marun: This pull request references Bugzilla bug 1886160, 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. |
|
/test e2e-aws-disruptive |
|
/test e2e-aws-disruptive |
|
/retest |
|
/test e2e-aws-disruptive |
|
/retest |
|
/test e2e-aws-disruptive |
2 similar comments
|
/test e2e-aws-disruptive |
|
/test e2e-aws-disruptive |
|
/retest |
|
/test e2e-aws-disruptive |
1 similar comment
|
/test e2e-aws-disruptive |
|
/retest |
2 similar comments
|
/retest |
|
/retest |
|
/test e2e-aws-disruptive |
3 similar comments
|
/test e2e-aws-disruptive |
|
/test e2e-aws-disruptive |
|
/test e2e-aws-disruptive |
|
/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. |
|
/test all |
|
/test e2e-gcp |
|
/test e2e-gcp |
|
/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. |
|
@marun: The following test 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/test-infra repository. I understand the commands that are listed here. |
|
/hold |
|
/test e2e-gcp |
1 similar comment
|
/test e2e-gcp |
|
/hold cancel |
|
@marun: All pull requests linked via external trackers have merged: Bugzilla bug 1886160 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. |
No description provided.