[action] [PR:17889] Disable PFC-WD during PCBB and some wmk test improvements#17991
Merged
mssonicbld merged 1 commit intosonic-net:202411from Apr 16, 2025
Merged
Conversation
…17889) * Improve validation so multiple failures can be reported. * Disable PFC-WD during PCBB tests. * Wait for PFC-WD to stop. * Remove packet aging code from pfcwd fixture.
11 tasks
Collaborator
Author
|
Original PR: #17889 |
Collaborator
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
Rerun failed jobs. |
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
Summary:
During flaky test analysis of:
Discovered that PFC-WD was enabled and being triggered during these tests. Added an auto-use fixture to disable PFC-WD and restore appropriately, similar to QOS SAI fixture.
Included the packet aging logic in case a relevant asic needs it going forward.
Changes:
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Validated: 1dfc735
Sample failure for new logging code:
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation