skip flaky IPv6 misc-provisioning tests #18806
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
amolpati30
added
No-CherryPick
| @@ -68,6 +68,7 @@ def assert_host_logs(channel, pattern): | |||
| @pytest.mark.on_premises_provisioning | |||
| @pytest.mark.ipv6_provisioning | |||
| @pytest.mark.rhel_ver_match(r'^(?!.*fips).*$') | |||
| @pytest.mark.skip(reason='The flaky test is skipped until support or a fix is implemented') | |||
There was a problem hiding this comment.
Since it would skip this test for both IPv4 and IPv6, and considering the provisioning fixture executions here for IPv6, I'd suggest to not skip this here and do this in CI instead, as we discussed offline.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are currently experiencing instability in some tests. Although we attempted to address the issue with certain solutions, the tests continue to fail or behave inconsistently. Due to this flakiness, the team has decided to temporarily skip these tests to ensure more reliable overall results. However, we are actively working on resolving the root cause of the flaky behavior to ensure these tests can be re-enabled and consistently pass in the future.