-
Notifications
You must be signed in to change notification settings - Fork 711
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
qos/test_buffer expects hardcoded vendor specific QoS settings #7016
Comments
@stephenxs take a look please |
Hi |
please clarify what DUT configuration you need |
BUFFER_QUEUE, BUFFER_PG, BUFFER_POOL, BUFFER_PROFILE tables. |
config from t1 setup...
Here I shorten a list to show interfaces with unique configs
|
Description
qos/test_buffer.py::test_buffer_deployment test has many expectations regarding QoS buffer profile settings like:
The issue is that aforementioned assignments are not static and may vary for different vendors. As result tests can pass for one platform but fail for another with message like below:
Looking on test body or origin PR it is not clear what test expectations are based on and why the test expects a given buffer profile to be assigned on a given pg/queue.
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Test pass or fail providing clear message on expected result and possible required per-vendor adaptation.
Additional information you deem important:
The text was updated successfully, but these errors were encountered: