Restrict detection/resolution time config to relevant ASIC #21586
Conversation
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
…b.com/dcaugher/sonic-mgmt into dcaugher-get-pfcwd-mind-your-own-asic
Collaborator
|
/azp run |
github-actions
bot
requested review from
isabelmsft,
xincunli-sonic and
yutongzhang-microsoft
|
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
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 # MIGSMSFT-1320
Type of change
Back port request
Approach
What is the motivation for this PR?
To fix a test case that fails unnecessarily.
How did you do it?
Restricted config changes to a particular ASIC.
How did you verify/test it?
Unable to at this time, asking for help.
Any platform specific information?
Applies only to multi-asic systems
Supported testbed topology if it's a new test case?
Documentation