cisco-8000: set 512bit time to a longer duration for cisco-8000 pfcwd tests using pfc_gen.py#16159
Merged
yejianquan merged 6 commits intosonic-net:masterfrom Jan 13, 2025
Merged
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
@abdosi can you help to take a look ? |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
sdszhang
reviewed
Jan 7, 2025
|
|
||
|
|
||
| @pytest.fixture(scope="function", autouse=False) | ||
| def set_pfc_time_cisco_8000( |
Contributor
There was a problem hiding this comment.
pls limit this change to Cisco T2 chassis only for now.
sdszhang
reviewed
Jan 7, 2025
| port) | ||
|
|
||
|
|
||
| def set_pfc_timer_cisco_8000(duthost, asic_id, script, port): |
Contributor
There was a problem hiding this comment.
pls limit this change to Cisco T2 chassis only for now.
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
@rraghav-cisco can you upload the test result. |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
sdszhang
approved these changes
Jan 12, 2025
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Jan 13, 2025
Description of PR Summary: Fixes the flakiness of pfc_gen in pfcwd scripts for cisco-8000. We use a new debug CLI script to force the DUT to wait longer in case of a miss in pfc packets from the fanout due to pfc_gen script. So even if the pfc_gen/fanout misses a couple of pfc frames to DUT, the dut would still not send out data packets. Approach What is the motivation for this PR? Flakiness of pfc-gen. Particularly with 400G links. How did you do it? We have added a new dshell based script that will force the DUT to wait before transmitting data in case of a miss in pfc pause frames. How did you verify/test it? Ran on our duts, with 100G and 400G. Any platform specific information? The new fix specific only to cisco-8000. co-authorized by: jianquanye@microsoft.com
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Jan 13, 2025
Description of PR Summary: Fixes the flakiness of pfc_gen in pfcwd scripts for cisco-8000. We use a new debug CLI script to force the DUT to wait longer in case of a miss in pfc packets from the fanout due to pfc_gen script. So even if the pfc_gen/fanout misses a couple of pfc frames to DUT, the dut would still not send out data packets. Approach What is the motivation for this PR? Flakiness of pfc-gen. Particularly with 400G links. How did you do it? We have added a new dshell based script that will force the DUT to wait before transmitting data in case of a miss in pfc pause frames. How did you verify/test it? Ran on our duts, with 100G and 400G. Any platform specific information? The new fix specific only to cisco-8000. co-authorized by: jianquanye@microsoft.com
Collaborator
|
Cherry-pick PR to 202411: #16468 |
Collaborator
|
Cherry-pick PR to 202405: #16469 |
This was referenced Jan 13, 2025
mssonicbld
pushed a commit
that referenced
this pull request
Jan 13, 2025
Description of PR Summary: Fixes the flakiness of pfc_gen in pfcwd scripts for cisco-8000. We use a new debug CLI script to force the DUT to wait longer in case of a miss in pfc packets from the fanout due to pfc_gen script. So even if the pfc_gen/fanout misses a couple of pfc frames to DUT, the dut would still not send out data packets. Approach What is the motivation for this PR? Flakiness of pfc-gen. Particularly with 400G links. How did you do it? We have added a new dshell based script that will force the DUT to wait before transmitting data in case of a miss in pfc pause frames. How did you verify/test it? Ran on our duts, with 100G and 400G. Any platform specific information? The new fix specific only to cisco-8000. co-authorized by: jianquanye@microsoft.com
mssonicbld
pushed a commit
that referenced
this pull request
Jan 15, 2025
Description of PR Summary: Fixes the flakiness of pfc_gen in pfcwd scripts for cisco-8000. We use a new debug CLI script to force the DUT to wait longer in case of a miss in pfc packets from the fanout due to pfc_gen script. So even if the pfc_gen/fanout misses a couple of pfc frames to DUT, the dut would still not send out data packets. Approach What is the motivation for this PR? Flakiness of pfc-gen. Particularly with 400G links. How did you do it? We have added a new dshell based script that will force the DUT to wait before transmitting data in case of a miss in pfc pause frames. How did you verify/test it? Ran on our duts, with 100G and 400G. Any platform specific information? The new fix specific only to cisco-8000. co-authorized by: jianquanye@microsoft.com
auspham
reviewed
Jan 23, 2025
| asic_arg = "" | ||
| if asic_id: | ||
| asic_arg = f"-n asic{asic_id}" | ||
| duthost.shell(f"show platform npu script {asic_arg} -s {script_name}") |
Contributor
There was a problem hiding this comment.
@rraghav-cisco i ran into this problem:
> raise RunAnsibleModuleFail("run module {} failed".format(self.module_name), res)
E tests.common.errors.RunAnsibleModuleFail: run module shell failed, Ansible Results =>
E failed = True
E changed = True
E rc = 2
E cmd = show platform npu script -s set_pfc_time.py
E start = 2025-01-23 04:05:01.590011
E end = 2025-01-23 04:05:03.007243
E delta = 0:00:01.417232
E msg = non-zero return code
E invocation = {'module_args': {'_raw_params': 'show platform npu script -s set_pfc_time.py', '_uses_shell': True, 'warn': False, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable': None, 'creates': None, 'removes': None, 'stdin': None}}
E _ansible_no_log = None
E stdout =
E stderr =
E Usage: show platform npu script [OPTIONS]
E Try "show platform npu script -h" for help.
E
E Error: Missing option "-n". Choose from:
E asic0,
E asic1,
E asic2.
cc @sdszhang
Contributor
Author
There was a problem hiding this comment.
@rraghav-cisco i ran into this problem:
> raise RunAnsibleModuleFail("run module {} failed".format(self.module_name), res) E tests.common.errors.RunAnsibleModuleFail: run module shell failed, Ansible Results => E failed = True E changed = True E rc = 2 E cmd = show platform npu script -s set_pfc_time.py E start = 2025-01-23 04:05:01.590011 E end = 2025-01-23 04:05:03.007243 E delta = 0:00:01.417232 E msg = non-zero return code E invocation = {'module_args': {'_raw_params': 'show platform npu script -s set_pfc_time.py', '_uses_shell': True, 'warn': False, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable': None, 'creates': None, 'removes': None, 'stdin': None}} E _ansible_no_log = None E stdout = E stderr = E Usage: show platform npu script [OPTIONS] E Try "show platform npu script -h" for help. E E Error: Missing option "-n". Choose from: E asic0, E asic1, E asic2.cc @sdszhang
11 tasks
nnelluri-cisco
pushed a commit
to nnelluri-cisco/sonic-mgmt
that referenced
this pull request
Mar 15, 2025
Description of PR Summary: Fixes the flakiness of pfc_gen in pfcwd scripts for cisco-8000. We use a new debug CLI script to force the DUT to wait longer in case of a miss in pfc packets from the fanout due to pfc_gen script. So even if the pfc_gen/fanout misses a couple of pfc frames to DUT, the dut would still not send out data packets. Approach What is the motivation for this PR? Flakiness of pfc-gen. Particularly with 400G links. How did you do it? We have added a new dshell based script that will force the DUT to wait before transmitting data in case of a miss in pfc pause frames. How did you verify/test it? Ran on our duts, with 100G and 400G. Any platform specific information? The new fix specific only to cisco-8000. co-authorized by: jianquanye@microsoft.com
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of PR
Summary:
Fixes the flakiness of pfc_gen in pfcwd scripts for cisco-8000. We use a new debug CLI script to force the DUT to wait longer in case of a miss in pfc packets from the fanout due to pfc_gen script. So even if the pfc_gen/fanout misses a couple of pfc frames to DUT, the dut would still not send out data packets.
Type of change
Back port request
Approach
What is the motivation for this PR?
Flakiness of pfc-gen. Particularly with 400G links.
How did you do it?
We have added a new dshell based script that will force the DUT to wait before transmitting data in case of a miss in pfc pause frames.
How did you verify/test it?
Ran on our duts, with 100G and 400G.
Any platform specific information?
The new fix specific only to cisco-8000.