[action] [PR:18516] [M1] Collect all upstream ports for ACL test#18543
Merged
mssonicbld merged 1 commit intosonic-net:202505from May 23, 2025
Merged
[action] [PR:18516] [M1] Collect all upstream ports for ACL test#18543mssonicbld merged 1 commit intosonic-net:202505from
mssonicbld merged 1 commit intosonic-net:202505from
Conversation
What is the motivation for this PR? In M1 topo, we have 2 upstream neighbor types: MA and MB. We need to collect all upstream ports to avoid packet capture flaky failure. How did you do it? Add function to read all up/down stream neighbor types. How did you verify/test it? Verified by ACL test on M1.
12 tasks
Collaborator
Author
|
Original PR: #18516 |
Collaborator
Author
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
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
2 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
Summary:
In M1 topo, we have 2 upstream neighbor types: MA and MB.
We need to collect all upstream ports to avoid packet capture flaky failure.
Type of change
Back port request
Approach
What is the motivation for this PR?
In M1 topo, we have 2 upstream neighbor types: MA and MB.
We need to collect all upstream ports to avoid packet capture flaky failure.
How did you do it?
Add function to read all up/down stream neighbor types.
How did you verify/test it?
Verified by ACL test on M1.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation