Improvising qos tests by tunning the qos params for single_asic, single_dut_multi_asic and multi_dut#8222
Conversation
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
pre-commit check is a mandatory check, please fix detected issues |
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
@vmittal-msft Could you check and review this PR ? |
415469e to
3385718
Compare
tests/qos/files/qos_params.j2c.yaml
Outdated
There was a problem hiding this comment.
Lets remove it. This will be fixed by BRCM CSP.
c0dc5c8 to
a67cc10
Compare
tests/qos/files/qos_params.j2c.yaml
Outdated
There was a problem hiding this comment.
please keep existing values as we will have fix for this.
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
@XuChen-MSFT ,@wsycqyz ,kindly review & approve |
|
@ansrajpu-git PR conflicts with 202205 branch |
|
Cherry-pick PR to 202305: #9703 |
…le_dut_multi_asic and multi_dut (sonic-net#8222) * QoS tunning for LossyQueueTest * Making assert specific to dnx for DscpQueueMapping qos_test fix flake8 errors flake8 issue resolved * Recommiting the changes of qos.yml to qos_params_j2c.yml * Reverting dscp to 7 as this is fixed in BRCM CSP * Revert "Making assert specific to dnx for DscpQueueMapping qos_test" This reverts commit dcbf90fa1bbdb3778d9ef86a202c30d86bd08114. * changing dscp value back to 8 * tx_enable/disable retry check corrected * Flake8 errore fixed * Making check to run only for chassis in LossyQueue * Adding check for sai_base for tx_enable/disable
…le_dut_multi_asic and multi_dut (#8222) (#9703) This PR is in continuation of PR# #8149 which was originally part of PR# #6946 The existing QoS (test_qos_sai.py) is written to accommodate a single asic on a single Dut. But, we require the same tests to be executed against a T2 chassis (with single/multi-asic linecards) and multi-asic pizza boxes. What is the motivation for this PR? 1.Qos test cases failed with intermittent errors How did you do it? Two issues are addressed here : 1.The dscp queue mapping for LossyQueue Test changed in config file to map to queue 1 of traffic-class instead of 0 since disabling the tx and filling up the queue 0 prevents the lacp packets going out and port channel goes down 2.During Qos test on transmission disable and enable, sometimes on test failure the port dangles in a transmission disable state and did not recover. Switching the step to enable the transmission port before the BCMSAI credit-watchdog enable , eradicate the test failure due to bad port state. How did you verify/test it? Executed qos testcases on for single_asic ,single_dut_multi_asic & multi_dut Co-authored-by: ansrajpu-git <[email protected]>
… single_asic, single_dut_multi_asic and multi_dut (sonic-net#8222) from master to 202205 * QoS tunning for LossyQueueTest * Making assert specific to dnx for DscpQueueMapping qos_test fix flake8 errors flake8 issue resolved * Recommiting the changes of qos.yml to qos_params_j2c.yml * Reverting dscp to 7 as this is fixed in BRCM CSP * Revert "Making assert specific to dnx for DscpQueueMapping qos_test" This reverts commit dcbf90fa1bbdb3778d9ef86a202c30d86bd08114. * changing dscp value back to 8 * tx_enable/disable retry check corrected * Flake8 errore fixed * Making check to run only for chassis in LossyQueue * Adding check for sai_base for tx_enable/disable
… single_asic, single_dut_multi_asic and multi_dut (#8222) from master to 202205 (#10209) Master PR #8222 QoS tunning for LossyQueueTest Recommiting the changes of qos.yml to qos_params_j2c.yml tx_enable/disable retry check corrected Making check to run only for chassis in LossyQueue Adding check for sai_base for tx_enable/disable
…le_dut_multi_asic and multi_dut (sonic-net#8222) * QoS tunning for LossyQueueTest * Making assert specific to dnx for DscpQueueMapping qos_test fix flake8 errors flake8 issue resolved * Recommiting the changes of qos.yml to qos_params_j2c.yml * Reverting dscp to 7 as this is fixed in BRCM CSP * Revert "Making assert specific to dnx for DscpQueueMapping qos_test" This reverts commit dcbf90fa1bbdb3778d9ef86a202c30d86bd08114. * changing dscp value back to 8 * tx_enable/disable retry check corrected * Flake8 errore fixed * Making check to run only for chassis in LossyQueue * Adding check for sai_base for tx_enable/disable
Description of PR
This PR is in continuation of PR# #8149
which was originally part of PR# #6946
The existing QoS (test_qos_sai.py) is written to accommodate a single asic on a single Dut. But, we require the same tests to be executed against a T2 chassis (with single/multi-asic linecards) and multi-asic pizza boxes.
Summary:
This PR is in continuation to above PR's mentioned
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
1.Qos test cases failed with intermittent errors
How did you do it?
Two issues are addressed here :
1.The dscp queue mapping for LossyQueue Test changed in config file to map to queue 1 of traffic-class instead of 0 since disabling the tx and filling up the queue 0 prevents the lacp packets going out and port channel goes down
2.During Qos test on transmission disable and enable, sometimes on test failure the port dangles in a transmission disable state and did not recover. Switching the step to enable the transmission port before the BCMSAI credit-watchdog enable , eradicate the test failure due to bad port state.
How did you verify/test it?
Executed qos testcases on for single_asic ,single_dut_multi_asic & multi_dut
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation