Port consistency checker to 202305 (f2cadae6)#17674
Merged
StormLiangMS merged 1 commit intosonic-net:202305from Apr 29, 2025
Merged
Port consistency checker to 202305 (f2cadae6)#17674StormLiangMS merged 1 commit intosonic-net:202305from
StormLiangMS merged 1 commit intosonic-net:202305from
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Ryangwaite
changed the title
hdwhdw
approved these changes
Apr 28, 2025
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.
Description of PR
Summary:
This is a manual backport of the consistency-checker utility from master at commit f2cadae. This includes the following two PR's:
Manually backported due to conflicts.
Type of change
Back port request
Approach
What is the motivation for this PR?
There were conflicts in creating cherry-pick backport PR's hence this manual approach.
How did you do it?
Cherry-picked the changes from the two PR's and resolved conflicts.
How did you verify/test it?
Ran test_upgrade_path and test_advanced_reboot.py on this branch. The feature in general has also been tested thoroughly on master.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation