[action] [PR:10031] Add t1-64-lag topo for test_lag_2.py::test_lag_db_status_with_po_update#10043
Merged
mssonicbld merged 1 commit intosonic-net:202305from Sep 15, 2023
Merged
Conversation
…te case (sonic-net#10031) What is the motivation for this PR? test_lag_2.py::test_lag_db_status_with_po_update supports t1-64-lag topo. How did you do it? Add t1-64-lag topo in conditions yaml file Signed-off-by: Zhaohui Sun <zhaohuisun@microsoft.com>
6 tasks
Collaborator
Author
|
Original PR: #10031 |
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.
…te case
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
test_lag_2.py::test_lag_db_status_with_po_update supports t1-64-lag topo.
How did you do it?
Add t1-64-lag topo in conditions yaml file
How did you verify/test it?
Choose t1-64-lag testbed and run test_lag_2.py::test_lag_db_status_with_po_update.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation