[e2e] Disable Pod DNS Resolution Test #884
Conversation
|
/lgtm |
test/e2e/network_test.go
Outdated
| // This test has 25% failure rate in CI. WINC-743 has been created to address | ||
| // this issue. Until we address WINC-743, this test has been temporarily | ||
| // disabled. | ||
| t.Skip("Pod DNS Resolution testing is disabled") |
There was a problem hiding this comment.
How about Pod DNS resolution is disabled pending flake investigation? Otherwise we are just stating the obvious and a t.Skip() would suffice.
This test has 25% failure rate in CIs. WINC-743 has been created to address this issue. Until we address WINC-743, this test has been temporarily disabled. Signed-off-by: selansen <esiva@redhat.com>
selansen
force-pushed
the
dns_test_diable
branch
from
01b04c1
to
fb6c016
Compare
|
/lgtm |
|
/approve |
|
/retest-required |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sebsoto, selansen 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 |
openshift-ci
bot
added
the
approved
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
@selansen: all tests passed! 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/test-infra repository. I understand the commands that are listed here. |
|
/cherry-pick release-4.10 |
|
/cherry-pick release-4.9 |
|
/cherry-pick release-4.8 |
|
/cherry-pick community-4.9 |
|
/cherry-pick community-4.8 |
|
@selansen: new pull request created: #886 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. |
|
@selansen: new pull request created: #887 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. |
|
@selansen: #884 failed to apply on top of branch "release-4.8": 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. |
|
@selansen: new pull request created: #888 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. |
|
@selansen: new pull request created: #889 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. |
|
/cherry-pick release-4.8 |
|
@jrvaldes: new pull request created: #970 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 test has 25% failure rate in CIs. WINC-743 has been created to address
this issue. Until we address WINC-743, this test has been temporarily
disabled.
Signed-off-by: selansen esiva@redhat.com