[action] [PR:15870] Update all port pfcwd storm test to make it more stable#19088
Merged
mssonicbld merged 1 commit intosonic-net:202411from Sep 3, 2025
Merged
Conversation
8 tasks
Collaborator
Author
|
Original PR: #15870 |
Collaborator
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run Azure.sonic-mgmt |
|
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
3 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
Update all port pfcwd storm test to make it more stable
Summary:
Fixes # (issue)
All port pfcwd storm test not stable enough.
Type of change
Back port request
Approach
What is the motivation for this PR?
Update all port pfcwd storm test is not stable engough.
How did you do it?
Optimize background traffic and arp resolvation.
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