[action] [PR:13283] Added a retry mechanism on hash test #17331
+91
−46
Conversation
This file contains 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
- What is the motivation for this PR? Preventing the hash test to fail in case of congestion on PTF. - How did you do it? Added a retry mechanism on hash test in case a packet wasn't sent correctly to the DUT, the retry will be applied on the same hash ket and same IPs - How did you verify/test it? Ran the hash test on ipv4/6 mode multiple times and ensured it was passing.
|
/azp run |
8 tasks
|
Original PR: #13283 |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Preventing the hash test to fail in case of congestion on PTF.
How did you do it?
Added a retry mechanism on hash test in case a packet wasn't sent correctly to the DUT, the retry will be applied on the same hash ket and same IPs
How did you verify/test it?
Ran the hash test on ipv4/6 mode multiple times and ensured it was passing.