Handle MegaBits speed for show int status <interface> output in test_update_speed testcase#7981
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:
|
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@sanjair-git PR conflicts with 202205 branch |
…update_speed testcase (sonic-net#7981) What is the motivation for this PR? Test case 'test_update_speed' in test_eth_interface.py fails, when the supported selected speed to apply on the interface is in 'Mbps' speed instead of 'Gbps'. How did you do it? If the current status speed after applying the patch is in 'Mbps', handle it as it is done for 'Gbps' speed. How did you verify/test it? Ran the 'test_update_speed' tests against a T2 chassis. Co-authored-by: rawal <amol.rawal@nokia.com>
…update_speed testcase (#7981) What is the motivation for this PR? Test case 'test_update_speed' in test_eth_interface.py fails, when the supported selected speed to apply on the interface is in 'Mbps' speed instead of 'Gbps'. How did you do it? If the current status speed after applying the patch is in 'Mbps', handle it as it is done for 'Gbps' speed. How did you verify/test it? Ran the 'test_update_speed' tests against a T2 chassis. Co-authored-by: rawal <amol.rawal@nokia.com>
…update_speed testcase (sonic-net#7981) What is the motivation for this PR? Test case 'test_update_speed' in test_eth_interface.py fails, when the supported selected speed to apply on the interface is in 'Mbps' speed instead of 'Gbps'. How did you do it? If the current status speed after applying the patch is in 'Mbps', handle it as it is done for 'Gbps' speed. How did you verify/test it? Ran the 'test_update_speed' tests against a T2 chassis. Co-authored-by: rawal <amol.rawal@nokia.com>
## Description of PR Summary: Fixes # (issue) ### Type of change - [ ] Bug fix - [ ] Testbed and Framework(new/improvement) - [x] Test case(new/improvement) ## Approach #### What is the motivation for this PR? ADO 17747379 to cherry-pick sonic-utilities PR to 202205 sonic-net/sonic-utilities#3051 requires 202205 sonic-mgmt test update. This PR cherry-picks the following PRs: #7981, #9878 (reads RDMA GCU conf file from DUT instead of copy of conf file in sonic-mgmt), #10214 (fix pfcwd test), #10241 (ensure operation is valid), #10756 (empty string edge case) #### How did you do it? Ensure the feature and tests are stable on 202305 and master #### How did you verify/test it? Monitored test results on 202305 and master for all platforms, manually ran tests on Cisco and Mellanox DUTs
Description of PR
Summary:
Fixes # (issue)
This PR fixes the issue when the supported selected speed to test for the interface is in Mbps instead of Gbps.
Type of change
Back port request
Approach
What is the motivation for this PR?
Test case 'test_update_speed' in test_eth_interface.py fails, when the supported selected speed to apply on the interface is in 'Mbps' speed instead of 'Gbps'.
How did you do it?
If the current status speed after applying the patch is in 'Mbps', handle it as it is done for 'Gbps' speed.
How did you verify/test it?
Ran the 'test_update_speed' tests against a T2 chassis.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation