Add t1-64-lag topo for test_lag_2.py::test_lag_db_status_with_po_update#10031
Merged
ZhaohuiS merged 1 commit intosonic-net:masterfrom Sep 15, 2023
Merged
Conversation
…te case Signed-off-by: Zhaohui Sun <zhaohuisun@microsoft.com>
lipxu
approved these changes
Sep 15, 2023
Contributor
lipxu
left a comment
lipxu
left a comment
There was a problem hiding this comment.
Does this case negatively support this topo or have we made enhancements to support it? thanks
Contributor
Author
@lipxu No, it should support t1-64-lag, but we missed it in condition yaml file before. |
Collaborator
|
@ZhaohuiS PR conflicts with 202012 branch |
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Sep 15, 2023
…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>
Collaborator
|
Cherry-pick PR to 202205: #10042 |
Merged
6 tasks
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Sep 15, 2023
…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>
Collaborator
|
Cherry-pick PR to 202305: #10043 |
Merged
6 tasks
6 tasks
mssonicbld
pushed a commit
that referenced
this pull request
Sep 15, 2023
…te case (#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>
mssonicbld
pushed a commit
that referenced
this pull request
Sep 15, 2023
…te case (#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>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Jan 25, 2024
…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>
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
4 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