-
Notifications
You must be signed in to change notification settings - Fork 909
Send more verification packets in packet trimming tests #21435
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Send more verification packets in packet trimming tests #21435
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
r12f
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR attached here slows down the draining time more, but it could be still not enough: https://github.com/Azure/sonic-mgmt.msft/pull/827/files.
bumping the packet count seems to be straightforward for the fix, hence approving.
@kperumalbfn @developfast , do you mind to also take a look at this PR?
| DUMMY_IPV6 = "8000::2" | ||
| DUMMY_MAC = "00:11:22:33:44:55" | ||
| PACKET_COUNT = 10 | ||
| PACKET_COUNT = 100 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
699a78f to
3fd5bd6
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@rgarofano-arista can you fix the PR checker failure? |
Signed-off-by: Ryan Garofano <[email protected]>
3fd5bd6 to
0a58d9d
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Cherry-pick PR to msft-202412: Azure/sonic-mgmt.msft#897 |
) Signed-off-by: Ryan Garofano <[email protected]>
|
Cherry-pick PR to 202511: #21541 |
) Signed-off-by: Ryan Garofano <[email protected]>
) Signed-off-by: Ryan Garofano <[email protected]> Signed-off-by: Dan Caugherty <[email protected]>
Signed-off-by: Ryan Garofano <[email protected]>
) Signed-off-by: Ryan Garofano <[email protected]> Signed-off-by: Nishanth Sampath Kumar <[email protected]>
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Verification for packet trimming tests was failing on th5. We found that trimming was not occurring because too many packets were leaking out of the egress queue despite the shaper being applied.
How did you do it?
By increasing the number of packets sent from 10 to 100 in the verification stage, we saw that trimming was occurring and the verification passed.
How did you verify/test it?
Verified that packet trimming tests were passing with the change.
Any platform specific information?
This issue was discovered when trying to support broadcom th5.
Supported testbed topology if it's a new test case?
Documentation