[action] [PR:12530] Fix qos/test_pfc_pause.py for dualtor-aa#13018
Merged
mssonicbld merged 1 commit intosonic-net:202311from May 29, 2024
Merged
[action] [PR:12530] Fix qos/test_pfc_pause.py for dualtor-aa#13018mssonicbld merged 1 commit intosonic-net:202311from
mssonicbld merged 1 commit intosonic-net:202311from
Conversation
8 tasks
Collaborator
Author
|
Original PR: #12530 |
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: Fix qos/test_pfc_pause.py for dualtor-aa
Fixes: #100
Type of change
Back port request
Approach
What is the motivation for this PR?
qos/test_pfc_pause.pyfails on dualtor-aaThis happens because the packets go to unselected ToR.
How did you do it?
Follow the same approach as in #11921
How did you verify/test it?
Verified on Arista-7260 platform with both dualtor-aa and dualtor topology.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation