Merged
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
94462d5 to
c50f616
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
c50f616 to
dc25877
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
theasianpianist
approved these changes
Apr 11, 2025
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
theasianpianist
approved these changes
Apr 12, 2025
* Teardown configurations after the test * Add an option to select the dpu to use for testing Signed-off-by: Prabhat Aravind <[email protected]>
* Orchagent needs routing_type to be programmed before ca_to_pa mappings can be programmed. This was exposed when adding the changes in sonic-mgmt to cleanup configurations at the end of the test. The fix here merely avoids the problem by configuring objects in the right order but this will need an orchagent fix as well to avoid stale object being left behind in ASIC_DB. Signed-off-by: Prabhat Aravind <[email protected]>
0c5d7e8 to
f87d34a
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
@mukeshmv please review. My PR had a conflict with yours. |
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
* DASH PL tests fixes * Teardown configurations after the test * Add an option to select the dpu to use for testing Signed-off-by: Prabhat Aravind <[email protected]>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
* DASH PL tests fixes * Teardown configurations after the test * Add an option to select the dpu to use for testing Signed-off-by: Prabhat Aravind <[email protected]> Signed-off-by: Aharon Malkin <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
* DASH PL tests fixes * Teardown configurations after the test * Add an option to select the dpu to use for testing Signed-off-by: Prabhat Aravind <[email protected]> Signed-off-by: Guy Shemesh <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
* DASH PL tests fixes * Teardown configurations after the test * Add an option to select the dpu to use for testing Signed-off-by: Prabhat Aravind <[email protected]> Signed-off-by: Guy Shemesh <[email protected]>
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:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
To make sure that configuration applied during the test is cleaned up properly at the end of the test.
How did you do it?
By adding cleanup logic for PL tests.
How did you verify/test it?
By running sonic-mgmt test PL test and verifying that the DASH objects programmed during the test are cleaned up at the end.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation