[asym_pfc]: Fix config parse according to latest changes #1190
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
Signed-off-by: Volodymyr Samotiy <[email protected]>
|
Would you mind to refer to the PR who cause this failure? |
liat-grozovik
approved these changes
Nov 3, 2019
Done. Updated PR description with this info. |
wendani
approved these changes
Nov 4, 2019
wendani
reviewed
Nov 4, 2019
liat-grozovik
approved these changes
Nov 6, 2019
yvolynets-mlnx
pushed a commit
to yvolynets-mlnx/sonic-mgmt
that referenced
this pull request
Dec 13, 2019
) Signed-off-by: Volodymyr Samotiy <[email protected]>
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: Volodymyr Samotiy [email protected]
Description of PR
Summary:
Fix config parser for asymmetric PFC according to latest changes
Type of change
Approach
How did you do it?
Recently QoS/buffer config format was changed so aligned parser in the test according to new format.
Changes that broke this test were introduced by the PR sonic-net/sonic-buildimage#3542.
How did you verify/test it?
Ran asymmetric PFC test
Any platform specific information?
N/A
Supported testbed topology if it's a new test case?
N/A
Documentation
N/A