Conversation
|
This pull request introduces 21 alerts and fixes 6 when merging 9462b8f into 345323c - view on LGTM.com new alerts:
fixed alerts:
|
|
This pull request introduces 3 alerts and fixes 7 when merging bcde48b into 345323c - view on LGTM.com new alerts:
fixed alerts:
|
|
retest this please |
|
There are quite some LGTM warnings, can you address these? |
|
This pull request introduces 3 alerts and fixes 7 when merging 4f02571 into 4cdc296 - view on LGTM.com new alerts:
fixed alerts:
|
|
This pull request fixes 7 alerts when merging 6ce66d6 into 4cdc296 - view on LGTM.com fixed alerts:
|
fixed |
|
retest this please |
|
Hello, I'm a part of team working on stabilizing tgen and have been going through this PR to understand the use cases being targeted with regards to PFC (using Ixia Test Ports). I looked at the test plan and TCs, and felt there were few areas where we could've achieved (IMHO) more complete validation:
I have uploaded a test script for reference (works against back-to-back connected Ixia Ports): https://github.com/open-traffic-generator/ixnetwork/blob/test-pfc/tests/pfc/test_pfc_pause_e2e.py I'm also curious if you think there's value in covering following separate cases:
|
|
|
||
| def get_egress_lossless_buffer_size(host_ans): | ||
| """ | ||
| Get egress losless buffer size of a switch |
| fanout_graph_facts, | ||
| duthosts, | ||
| rand_one_dut_hostname): |
There was a problem hiding this comment.
can you fix the alignment?
|
@baiwei0427 , can you also include the check to ensure that the DUT sends PFC to the Tx port? That can be addressed in a separate PR |
I agree with you. Our current test plan and implementation cannot fully verify all the functionalities of PFC. Let's update the test plan and add some PFC tests in the separate PRs. |
This reverts commit 49625a1.
Signed-off-by: Neetha John <[email protected]> Fixes the error seen during test case collection introduced by #2599. Initialize the variable as a list https://sonic-jenkins.westus2.cloudapp.azure.com/job/common/job/sonic-mgmt-testing/job/sonic-mgmt-pr/2462/consoleFull How did you verify/test it? Tried test case collection with the fix. No longer seeing the error
Signed-off-by: Wei Bai [email protected]
Description of PR
Summary: Add PFC test cases implemented using Tgen API & Update Tgen sample script
Fixes # (issue)
Type of change
Approach
What is the motivation for this PR?
We need PFC test cases
How did you do it?
How did you verify/test it?
I did test using SONiC switches and IXIA chassis. The Tgen API version is 0.0.64.
Any platform specific information?
Supported testbed topology if it's a new test case?
T0 topology using IXIA chassis as the fanout
Documentation
https://github.com/Azure/sonic-mgmt/blob/master/docs/pfc/GLOBAL_PAUSE_README.md
https://github.com/Azure/sonic-mgmt/blob/master/docs/pfc/PFC_PAUSE_LOSSLESS_README.md
https://github.com/Azure/sonic-mgmt/blob/master/docs/pfc/PFC_PAUSE_LOSSY_README.md