Enhance generic hash packet sending function#14139
Merged
bingwang-ms merged 1 commit intosonic-net:masterfrom Oct 29, 2024
Merged
Enhance generic hash packet sending function#14139bingwang-ms merged 1 commit intosonic-net:masterfrom
bingwang-ms merged 1 commit intosonic-net:masterfrom
Conversation
Contributor
|
Do other branch need this PR? |
2b76012 to
8218733
Compare
Contributor
Author
Re-triggered. The test had been supported since 202311. |
8218733 to
3307ff2
Compare
1. In case of a weak nic, when packet is not received, resend the packet 2. Loop more times to make hash result more stable Change-Id: I89bfa1e4de43e281d82d736b102dc33a55a8e089
3307ff2 to
8feda37
Compare
Contributor
Author
|
/azpw run |
Collaborator
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
/azpw run |
Collaborator
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
bingwang-ms
reviewed
Oct 23, 2024
bingwang-ms
approved these changes
Oct 29, 2024
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Oct 29, 2024
1. In case of a weak nic, when packet is not received, resend the packet 2. Loop more times to make hash result more stable Change-Id: I89bfa1e4de43e281d82d736b102dc33a55a8e089
Collaborator
|
Cherry-pick PR to 202405: #15242 |
8 tasks
mssonicbld
pushed a commit
that referenced
this pull request
Oct 29, 2024
1. In case of a weak nic, when packet is not received, resend the packet 2. Loop more times to make hash result more stable Change-Id: I89bfa1e4de43e281d82d736b102dc33a55a8e089
sreejithsreekumaran
pushed a commit
to sreejithsreekumaran/sonic-mgmt
that referenced
this pull request
Nov 15, 2024
1. In case of a weak nic, when packet is not received, resend the packet 2. Loop more times to make hash result more stable Change-Id: I89bfa1e4de43e281d82d736b102dc33a55a8e089
yutongzhang-microsoft
pushed a commit
to yutongzhang-microsoft/sonic-mgmt
that referenced
this pull request
Nov 21, 2024
1. In case of a weak nic, when packet is not received, resend the packet 2. Loop more times to make hash result more stable Change-Id: I89bfa1e4de43e281d82d736b102dc33a55a8e089
11 tasks
mssonicbld
added a commit
to mssonicbld/sonic-mgmt.msft
that referenced
this pull request
Aug 11, 2025
…t correctly sent to the DUT <!-- Please make sure you've read and understood our contributing guidelines; https://github.com/sonic-net/SONiC/blob/gh-pages/CONTRIBUTING.md Please provide following information to help code review process a bit easier: --> ### Description of PR <!-- - Please include a summary of the change and which issue is fixed. - Please also include relevant motivation and context. Where should reviewer start? background context? - List any dependencies that are required for this change. --> In case of a weak nic, when a packet is not received, resend the packet Related PR: sonic-net/sonic-mgmt#14139 Summary: Fixes # (issue) ### Type of change <!-- - Fill x for your type of change. - e.g. - [x] Bug fix --> - [ ] Bug fix - [ ] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [x] Test case improvement ### Back port request - [ ] 202012 - [ ] 202205 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 ### Approach #### What is the motivation for this PR? Avoid failing the test in case of a packet wasn't received because of a weak NIC #### How did you do it? Add a retry sending traffic in case a packet wasn't received #### How did you verify/test it? Ran test in a loop to ensure its stability #### Any platform specific information? #### Supported testbed topology if it's a new test case? ### Documentation <!-- (If it's a new feature, new test case) Did you update documentation/Wiki relevant to your implementation? Link to the wiki page? -->
11 tasks
mssonicbld
added a commit
to Azure/sonic-mgmt.msft
that referenced
this pull request
Aug 11, 2025
…in case packet wasn't correctly sent to the DUT (#641) <!-- Please make sure you've read and understood our contributing guidelines; https://github.com/sonic-net/SONiC/blob/gh-pages/CONTRIBUTING.md Please provide following information to help code review process a bit easier: --> ### Description of PR <!-- - Please include a summary of the change and which issue is fixed. - Please also include relevant motivation and context. Where should reviewer start? background context? - List any dependencies that are required for this change. --> In case of a weak nic, when a packet is not received, resend the packet Related PR: sonic-net/sonic-mgmt#14139 Summary: Fixes # (issue) ### Type of change <!-- - Fill x for your type of change. - e.g. - [x] Bug fix --> - [ ] Bug fix - [ ] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [x] Test case improvement ### Back port request - [ ] 202012 - [ ] 202205 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 ### Approach #### What is the motivation for this PR? Avoid failing the test in case of a packet wasn't received because of a weak NIC #### How did you do it? Add a retry sending traffic in case a packet wasn't received #### How did you verify/test it? Ran test in a loop to ensure its stability #### Any platform specific information? #### Supported testbed topology if it's a new test case? ### Documentation <!-- (If it's a new feature, new test case) Did you update documentation/Wiki relevant to your implementation? Link to the wiki page? -->
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Aug 12, 2025
…t correctly sent to the DUT (sonic-net#18012) In case of a weak nic, when a packet is not received, resend the packet Related PR: sonic-net#14139
11 tasks
ashutosh-agrawal
pushed a commit
to ashutosh-agrawal/sonic-mgmt
that referenced
this pull request
Aug 14, 2025
…t correctly sent to the DUT (sonic-net#18012) In case of a weak nic, when a packet is not received, resend the packet Related PR: sonic-net#14139
vidyac86
pushed a commit
to vidyac86/sonic-mgmt
that referenced
this pull request
Oct 23, 2025
…t correctly sent to the DUT (sonic-net#18012) In case of a weak nic, when a packet is not received, resend the packet Related PR: sonic-net#14139
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
…t correctly sent to the DUT (sonic-net#18012) In case of a weak nic, when a packet is not received, resend the packet Related PR: sonic-net#14139 Signed-off-by: opcoder0 <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
…t correctly sent to the DUT (sonic-net#18012) In case of a weak nic, when a packet is not received, resend the packet Related PR: sonic-net#14139 Signed-off-by: Guy Shemesh <[email protected]>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
…t correctly sent to the DUT (sonic-net#18012) In case of a weak nic, when a packet is not received, resend the packet Related PR: sonic-net#14139 Signed-off-by: Aharon Malkin <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
…t correctly sent to the DUT (sonic-net#18012) In case of a weak nic, when a packet is not received, resend the packet Related PR: sonic-net#14139 Signed-off-by: Guy Shemesh <[email protected]>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Jan 13, 2026
…t correctly sent to the DUT (sonic-net#18012) In case of a weak nic, when a packet is not received, resend the packet Related PR: sonic-net#14139
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
…t correctly sent to the DUT (sonic-net#18012) In case of a weak nic, when a packet is not received, resend the packet Related PR: sonic-net#14139 Signed-off-by: Guy Shemesh <[email protected]>
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Feb 2, 2026
…t correctly sent to the DUT (sonic-net#18012) In case of a weak nic, when a packet is not received, resend the packet Related PR: sonic-net#14139 Signed-off-by: Yael Tzur <[email protected]>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Mar 27, 2026
…t correctly sent to the DUT (sonic-net#18012) In case of a weak nic, when a packet is not received, resend the packet Related PR: sonic-net#14139
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
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
Enhance generic hash script packet sending function
1. In case of a weak nic, when packet is not received, resend the packet
2. Loop more times to make hash result more stable
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Some weak nic would failed to send packet incidentally
How did you do it?
Send more packets
How did you verify/test it?
Run it in internal regression
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation