Add public sad multi hop test case #16533
Open
Conversation
This file contains 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
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ryanzhu706
approved these changes
Jan 28, 2025
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:
Adds sad case test coverage to upgrades. These are the same cases as in
tests/upgrade_path/test_upgrade_path.py::test_warm_upgrade_sad_pathbut ported to multi-hop.Type of change
Back port request
Approach
What is the motivation for this PR?
Add more test coverage
How did you do it?
Ported the sad case for A->B upgrade (
tests/upgrade_path/test_upgrade_path.py::test_warm_upgrade_sad_path) to multi-hopHow did you verify/test it?
Tested on internal pipelines
Any platform specific information?
N/A
Supported testbed topology if it's a new test case?
t0*
Documentation