[202205][everflow][m0] Add support for m0 in everflow to simulate both t0 and t1 #7618#7638
Merged
yaqiangz merged 2 commits intosonic-net:202205from Mar 3, 2023
Merged
Conversation
Blueve
approved these changes
Mar 3, 2023
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
2 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:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Manually cherry-pick and resolve conflicts of this PR: #7618
In current everflow test for m0, just simulate scenario that m0 device performs like t1. But m0 is like both t1 and t0.
How did you do it?
Add support for m0 in everflow test to simulate both t0 and t1 scenario
How did you verify/test it?
Run tests on m0 topo and t0 topo
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation