-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Disable flaky tests on OpenStack #24330
Conversation
In order to increase chances to get a voting CI for OpenStack soon, I propose to skip Network Granular Check tests that are intermittently failing on our infrastructure. This commit must be reverted and the issue properly investigated once the minimum result of a voting CI is achieved. ref.: https://bugzilla.redhat.com/show_bug.cgi?id=1763936 ref.: openshift#24313
/retest |
1 similar comment
/retest |
This is fine for me |
/retest |
/cherry-pick release-4.3 |
@pierreprinetti: once the present PR merges, I will cherry-pick it on top of release-4.3 in a new PR and assign it to you. 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. |
/approve |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: knobunc, pierreprinetti 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 |
/retest Please review the full test history for this PR and help us cut down flakes. |
11 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. |
/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. |
/cherry-pick release-4.3 |
@nee1esh: new pull request created: #24340 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. |
Those tests are constantly failing on our infrastructure during conformance runs. This commit is due to the removal of those test from the Flaky on, openshift#24313. And the PR from openstack who experience the same results on there CI runs openshift#24330. Signed-off-by: Gal Zaidman <gzaidman@redhat.com>
As the network issue is expected to be now [resolved][1], these tests have no reason to be skipped. Reverts openshift#24330 [1]: openshift/installer#3027
As the network issue is expected to be now [resolved][1], these tests have no reason to be skipped. Reverts openshift#24330 [1]: openshift/installer#3027
As the network issue is expected to be now [resolved][1], these tests have no reason to be skipped. Reverts openshift/origin#24330 [1]: openshift/installer#3027
As the network issue is expected to be now [resolved][1], these tests have no reason to be skipped. Reverts openshift#24330 [1]: openshift/installer#3027
In order to increase chances to get a voting CI for OpenStack soon, I
propose to skip Network Granular Check tests that are intermittently
failing on our infrastructure.
This commit must be reverted and the issue properly investigated once
the minimum result of a voting CI is achieved.
ref.: https://bugzilla.redhat.com/show_bug.cgi?id=1763936
ref.: #24313
The bug reference is not in the PR title nor leading the commit message, because this proposed change does not fix it.
/assign @smarterclayton
/cc @knobunc
@danwinship Do you think this work for OpenStack? Sorry I am not familiar with the skip logic, and I could not find specific documentation on the matter.