Enable dip_sip and mtu test on DT2 topology#21301
Merged
bingwang-ms merged 1 commit intosonic-net:masterfrom Dec 16, 2025
Merged
Enable dip_sip and mtu test on DT2 topology#21301bingwang-ms merged 1 commit intosonic-net:masterfrom
bingwang-ms merged 1 commit intosonic-net:masterfrom
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
auspham
approved these changes
Nov 11, 2025
bingwang-ms
added a commit
to Azure/sonic-mgmt.msft
that referenced
this pull request
Dec 16, 2025
Collaborator
Author
|
Included in 202503 by PR Azure/sonic-mgmt.msft#935 |
selldinesh
pushed a commit
to selldinesh/sonic-mgmt
that referenced
this pull request
Dec 18, 2025
Signed-off-by: selldinesh <dinesh.sellappan@keysight.com>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
vrajeshe
pushed a commit
to Akshath-17/sonic-mgmt
that referenced
this pull request
Jan 4, 2026
Signed-off-by: Venkata Gouri Rajesh Etla <vrajeshe@cisco.com>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Jan 13, 2026
yifan-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Jan 14, 2026
Signed-off-by: YiFan Wang <yifan@nexthop.ai>
PriyanshTratiya
pushed a commit
to PriyanshTratiya/sonic-mgmt
that referenced
this pull request
Jan 21, 2026
Signed-off-by: Priyansh Tratiya <ptratiya@microsoft.com>
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Feb 2, 2026
Signed-off-by: Yael Tzur <ytzur@nvidia.com>
auspham
pushed a commit
to auspham/sonic-mgmt
that referenced
this pull request
Feb 3, 2026
Signed-off-by: bingwang <bingwang@microsoft.com>
abhishek-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Feb 6, 2026
rraghav-cisco
pushed a commit
to rraghav-cisco/sonic-mgmt
that referenced
this pull request
Feb 13, 2026
Signed-off-by: Raghavendran Ramanathan <rraghav@cisco.com>
anilal-amd
pushed a commit
to anilal-amd/anilal-forked-sonic-mgmt
that referenced
this pull request
Feb 19, 2026
Signed-off-by: Zhuohui Tan <zhuohui.tan@amd.com>
abhishek-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Mar 17, 2026
Signed-off-by: Abhishek <abhishek@nexthop.ai>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Mar 27, 2026
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:
This PR is to enable two tests on LT2 and FT2.
Type of change
Back port request
Approach
What is the motivation for this PR?
This PR is to enable two tests on LT2 and FT2.
How did you do it?
tests/common/plugins/conditional_mark/tests_mark_conditions.yamlto addLT2andFT2into supported topologiesLT2andFT2to topology markerHow did you verify/test it?
The change is verified on a physical testbed.
Any platform specific information?
No.
Supported testbed topology if it's a new test case?
Not a new test.
Documentation