[drop counters] Fix drop count tests to respect multi-DUT setups #2868
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
Signed-off-by: Danny Allen <daall@microsoft.com>
neethajohn
approved these changes
Jan 26, 2021
yxieca
approved these changes
Jan 26, 2021
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.
Signed-off-by: Danny Allen daall@microsoft.com
Description of PR
Summary: Fix drop count tests to respect multi-DUT setups
Type of change
Approach
What is the motivation for this PR?
There is a mismatch b/w which DUT we are sending traffic to and which DUT we are checking for drops because we aren't using the right fixtures to access DUTs in a multi-DUT setup.
How did you do it?
Added duthosts and rand_one_dut_hostname, in-line with the rest of the
sonic-mgmttests.How did you verify/test it?
Ran tests on a multi-DUT testbed and validated that the tests are passing.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation