[action] [PR:22259] Change dummy ip for fill packets to eliminate false positives#1025
Merged
mssonicbld merged 1 commit intoAzure:202412from Feb 18, 2026
Merged
Conversation
<!-- 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. --> Summary: Fixes # (issue) ### Type of change <!-- - Fill x for your type of change. - e.g. - [x] Bug fix --> - [x] Bug fix - [ ] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [ ] Test case improvement ### Back port request - [ ] 202205 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [x] 202412 - [ ] 202505 - [x] 202511 ### Approach #### What is the motivation for this PR? We were seeing failures in packet trimming tests when verifying UDP packets. This is because the shaper on TH5 is still sending a few packets a second that were used to fill up the buffer (simulating congestion) and these packets are nearly identical to the UDP packets used to verify trimming. This is leading to false positives where a packet that was used to fill the buffer is being detected as a "trimmed" packet when packet trimming is turned off. #### How did you do it? Fixed this by changing the dummy ip for the packets used to fill the buffer, meaning they won't be mistaken for a packet that the test sends to verify trimming. #### How did you verify/test it? Verified that the failure goes away with the change. #### 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? -->
Collaborator
Author
|
Original PR: sonic-net/sonic-mgmt#22259 |
Collaborator
Author
|
/azp run |
13 tasks
|
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
1 participant
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?
We were seeing failures in packet trimming tests when verifying UDP packets. This is because the shaper on TH5 is still sending a few packets a second that were used to fill up the buffer (simulating congestion) and these packets are nearly identical to the UDP packets used to verify trimming. This is leading to false positives where a packet that was used to fill the buffer is being detected as a "trimmed" packet when packet trimming is turned off.
How did you do it?
Fixed this by changing the dummy ip for the packets used to fill the buffer, meaning they won't be mistaken for a packet that the test sends to verify trimming.
How did you verify/test it?
Verified that the failure goes away with the change.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation