[action] [PR:16197] feat: add one_dut fixture to only use one dut #16211
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
Description of PR Summary: Currently, test_pfc_pause_single_lossy_prio and test_pfc_pause_single_lossy_prio_reboot are using more parameters than its needed, resulting in a longer execution time Fixes # (issue) 30562817 Approach What is the motivation for this PR? Reducing the number of DUT but still give enough priorities for coverage How did you do it? Modify the current fixture to add an option to pick 1 DUT for testing only How did you verify/test it? physical testbed Signed-off-by: Austin Pham <[email protected]>
|
/azp run |
8 tasks
|
Original PR: #16197 |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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:
Currently, test_pfc_pause_single_lossy_prio and test_pfc_pause_single_lossy_prio_reboot are using more parameters than its needed, resulting in a longer execution time
Fixes # (issue) 30562817
Type of change
Back port request
Approach
What is the motivation for this PR?
Reducing the number of DUT but still give enough priorities for coverage
How did you do it?
Modify the current fixture to add an option to pick 1 DUT for testing only
How did you verify/test it?
physical testbed
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation