-
Notifications
You must be signed in to change notification settings - Fork 740
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update WRR test to support qos remapping #6737
Conversation
The pre-commit check detected issues in the files touched by this pull request. For old issues, it is not mandatory to fix them because they were not caused by this change. It is unfair to blame Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
This pull request introduces 1 alert when merging d24fcd1 into 5990a18 - view on LGTM.com new alerts:
|
The pre-commit check detected issues in the files touched by this pull request. For old issues, it is not mandatory to fix them because they were not caused by this change. It is unfair to blame Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
This pull request introduces 1 alert when merging 72fc936 into f5cca01 - view on LGTM.com new alerts:
|
The change is verified on dualtor and T1 testbed, with and without remap. |
* Update WRR test to support qos remapping
Description of PR
Summary:
Fixes # (issue)
This PR is to update
testQosSaiDwrr
to support qos remapping scenario.When qos remapping is enabled, the QoS map is different from before.
When the remap is enabled, we have below map
So the test script need to be updated.
Type of change
Back port request
Approach
What is the motivation for this PR?
This PR is to update
testQosSaiDwrr
to support qos remapping scenario.How did you do it?
Update test script to to use different testing DSCP values.
How did you verify/test it?
Verified on an Arista-7050cx3 dualtor testbed.
Any platform specific information?
No.
Supported testbed topology if it's a new test case?
No.
Documentation