[action] [PR:18071] Mark xfail for generic hash test in isolated topo#18086
Merged
mssonicbld merged 1 commit intosonic-net:202411from Apr 23, 2025
Merged
[action] [PR:18071] Mark xfail for generic hash test in isolated topo#18086mssonicbld merged 1 commit intosonic-net:202411from
mssonicbld merged 1 commit intosonic-net:202411from
Conversation
What is the motivation for this PR? Mark xfail for flaky hashing behavior when using a specific combination of hash field and algorithm, such as CRC-INNER_L4_DST_PORT-ipv4-ipv6-nvgre. How did you do it? Mark test_generic_test.py as xfail in mark conditions yaml file How did you verify/test it? Verified it in nightly test run. Any platform specific information? str4-sn5600-1 Supported testbed topology if it's a new test case? t0-isolated-u16d16s1
11 tasks
Collaborator
Author
|
Original PR: #18071 |
Collaborator
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of PR
Summary: Mark xfail for flaky hashing behavior when using a specific combination of hash field and algorithm, such as CRC-INNER_L4_DST_PORT-ipv4-ipv6-nvgre.
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Mark xfail for flaky hashing behavior when using a specific combination of hash field and algorithm, such as CRC-INNER_L4_DST_PORT-ipv4-ipv6-nvgre.
How did you do it?
Mark test_generic_test.py as xfail in mark conditions yaml file
How did you verify/test it?
Verified it in nightly test run.
Any platform specific information?
str4-sn5600-1
Supported testbed topology if it's a new test case?
t0-isolated-u16d16s1
Documentation