[tests/copp]: Fix copp tests #12836

prabhataravind · 2024-05-13T16:47:32Z

Description of PR

This PR does the following:

Enhance copp test cases so that they pass consistently on Broadcom platforms.
- For Broadcom platforms, when BGP and IP2ME traps are removed, BGP packets hit the default trap group, so a new
  DefaultPolicy is introduced in check_constraints specifically for Broadcom ASIC types. The test logic for non-Broadcom
  platforms is left unchanged. A necessary side change of this is that the CIR for default trap needs to be changed to a
  value other than 600 only for the test. This is reverted back at the end of the test.
Remove xfail for copp tests on broadcom platforms
Skip updating default sonic config for queue4_group3 in scripts/update_copp_config.py as the new rate-limit for this copp
group is lower than the default value of 600 PPS used by copp tests. This value is 300PPS for Mgmt devices and 100 PPS for
other devices. The constraint checks for protocols that map to queue4_group3 are also changed accordingly in
ansible/roles/test/files/ptftests/py3/copp_tests.py

Summary:
Fixes # 27262099

Type of change

Bug fix
Testbed and Framework(new/improvement)
Test case(new/improvement)

Back port request

Approach

What is the motivation for this PR?

When BGP and IP2ME traps are removed, BGP packets hit the default trap group on broadcom platforms and trap to CPU queue0. This change modifies copp test to verify this behavior.

How did you do it?

By changing the rate limit used in the test for default trap group, it is easy to verify that packets are hitting that trap group. If all trap groups use the same rate limit of 600 pps as is done currently, it is rather difficult to identify which trap group got hit.

How did you verify/test it?

By running tests locally and using azure pipeline

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

mssonicbld · 2024-05-13T16:48:42Z

The pre-commit check detected issues in the files touched by this pull request.
The pre-commit check is a mandatory check, please fix detected issues.

Detailed pre-commit check results:
trim trailing whitespace.................................................Passed fix end of files.........................................................Passed check yaml...............................................................Passed check for added large files..............................................Passed check python ast.........................................................Passed flake8...................................................................Failed - hook id: flake8 - exit code: 1 ansible/roles/test/files/ptftests/py3/copp_tests.py:533:1: E303 too many blank lines (3) ansible/roles/test/files/ptftests/py3/copp_tests.py:534:1: E302 expected 2 blank lines, found 3 flake8...............................................(no files to check)Skipped check conditional mark sort..............................................Passed

To run the pre-commit checks locally, you can follow below steps:

Ensure that default python is python3. In sonic-mgmt docker container, default python is python2. You can run
the check by activating the python3 virtual environment in sonic-mgmt docker container or outside of sonic-mgmt
docker container.
Ensure that the pre-commit package is installed:

sudo pip install pre-commit

Go to repository root folder
Install the pre-commit hooks:

pre-commit install

Use pre-commit to check staged file:

pre-commit

Alternatively, you can check committed files using:

pre-commit run --from-ref <commit_id> --to-ref <commit_id>

mssonicbld · 2024-06-24T23:10:49Z

The pre-commit check detected issues in the files touched by this pull request.
The pre-commit check is a mandatory check, please fix detected issues.

Detailed pre-commit check results:
trim trailing whitespace.................................................Passed fix end of files.........................................................Passed check yaml...............................................................Passed check for added large files..............................................Passed check python ast.........................................................Passed flake8...................................................................Failed - hook id: flake8 - exit code: 1 ansible/roles/test/files/ptftests/py3/copp_tests.py:561:1: E303 too many blank lines (3) ansible/roles/test/files/ptftests/py3/copp_tests.py:562:1: E302 expected 2 blank lines, found 3 flake8...............................................(no files to check)Skipped check conditional mark sort..............................................Passed

To run the pre-commit checks locally, you can follow below steps:

Ensure that default python is python3. In sonic-mgmt docker container, default python is python2. You can run
the check by activating the python3 virtual environment in sonic-mgmt docker container or outside of sonic-mgmt
docker container.
Ensure that the pre-commit package is installed:

sudo pip install pre-commit

Go to repository root folder
Install the pre-commit hooks:

pre-commit install

Use pre-commit to check staged file:

pre-commit

Alternatively, you can check committed files using:

pre-commit run --from-ref <commit_id> --to-ref <commit_id>

mssonicbld · 2024-06-24T23:32:17Z

The pre-commit check detected issues in the files touched by this pull request.
The pre-commit check is a mandatory check, please fix detected issues.

Detailed pre-commit check results:
trim trailing whitespace.................................................Passed fix end of files.........................................................Passed check yaml...............................................................Passed check for added large files..............................................Passed check python ast.........................................................Passed flake8...................................................................Failed - hook id: flake8 - exit code: 1 ansible/roles/test/files/ptftests/py3/copp_tests.py:561:1: E303 too many blank lines (3) ansible/roles/test/files/ptftests/py3/copp_tests.py:562:1: E302 expected 2 blank lines, found 3 flake8...............................................(no files to check)Skipped check conditional mark sort..............................................Passed

To run the pre-commit checks locally, you can follow below steps:

Ensure that default python is python3. In sonic-mgmt docker container, default python is python2. You can run
the check by activating the python3 virtual environment in sonic-mgmt docker container or outside of sonic-mgmt
docker container.
Ensure that the pre-commit package is installed:

sudo pip install pre-commit

Go to repository root folder
Install the pre-commit hooks:

pre-commit install

Use pre-commit to check staged file:

pre-commit

Alternatively, you can check committed files using:

pre-commit run --from-ref <commit_id> --to-ref <commit_id>

Signed-off-by: Prabhat Aravind <paravind@microsoft.com>

This reverts commit 31101a5.

prsunny

Overall lgtm, @StormLiangMS , @ZhaohuiS , can one of you review and signoff?

ansible/roles/test/files/ptftests/py3/copp_tests.py

mssonicbld · 2024-07-02T02:09:16Z

The pre-commit check detected issues in the files touched by this pull request.
The pre-commit check is a mandatory check, please fix detected issues.

Detailed pre-commit check results:
trim trailing whitespace.................................................Passed fix end of files.........................................................Passed check yaml...............................................................Passed check for added large files..............................................Passed check python ast.........................................................Passed flake8...................................................................Failed - hook id: flake8 - exit code: 1 ansible/roles/test/files/ptftests/py3/copp_tests.py:267:121: E501 line too long (128 > 120 characters) ansible/roles/test/files/ptftests/py3/copp_tests.py:268:21: E127 continuation line over-indented for visual indent ansible/roles/test/files/ptftests/py3/copp_tests.py:278:21: E127 continuation line over-indented for visual indent ansible/roles/test/files/ptftests/py3/copp_tests.py:540:121: E501 line too long (128 > 120 characters) ansible/roles/test/files/ptftests/py3/copp_tests.py:541:21: E127 continuation line over-indented for visual indent ansible/roles/test/files/ptftests/py3/copp_tests.py:551:21: E127 continuation line over-indented for visual indent ansible/roles/test/files/ptftests/py3/copp_tests.py:561:121: E501 line too long (129 > 120 characters) ansible/roles/test/files/ptftests/py3/copp_tests.py:562:121: E501 line too long (131 > 120 characters) flake8...............................................(no files to check)Skipped check conditional mark sort..............................................Passed

To run the pre-commit checks locally, you can follow below steps:

Ensure that default python is python3. In sonic-mgmt docker container, default python is python2. You can run
the check by activating the python3 virtual environment in sonic-mgmt docker container or outside of sonic-mgmt
docker container.
Ensure that the pre-commit package is installed:

sudo pip install pre-commit

Go to repository root folder
Install the pre-commit hooks:

pre-commit install

Use pre-commit to check staged file:

pre-commit

Alternatively, you can check committed files using:

pre-commit run --from-ref <commit_id> --to-ref <commit_id>

ZhaohuiS · 2024-07-02T06:10:57Z

@prabhataravind could you please fix the pre-commit failures?
flake8...................................................................Failed

hook id: flake8
exit code: 1

ansible/roles/test/files/ptftests/py3/copp_tests.py:267:121: E501 line too long (128 > 120 characters)
ansible/roles/test/files/ptftests/py3/copp_tests.py:268:21: E127 continuation line over-indented for visual indent
ansible/roles/test/files/ptftests/py3/copp_tests.py:278:21: E127 continuation line over-indented for visual indent
ansible/roles/test/files/ptftests/py3/copp_tests.py:540:121: E501 line too long (128 > 120 characters)
ansible/roles/test/files/ptftests/py3/copp_tests.py:541:21: E127 continuation line over-indented for visual indent
ansible/roles/test/files/ptftests/py3/copp_tests.py:551:21: E127 continuation line over-indented for visual indent
ansible/roles/test/files/ptftests/py3/copp_tests.py:561:121: E501 line too long (129 > 120 characters)
ansible/roles/test/files/ptftests/py3/copp_tests.py:562:121: E501 line too long (131 > 120 characters)

mssonicbld · 2024-07-02T06:11:35Z

The pre-commit check detected issues in the files touched by this pull request.
The pre-commit check is a mandatory check, please fix detected issues.

Detailed pre-commit check results:
trim trailing whitespace.................................................Passed fix end of files.........................................................Passed check yaml...............................................................Passed check for added large files..............................................Passed check python ast.........................................................Passed flake8...................................................................Failed - hook id: flake8 - exit code: 1 ansible/roles/test/files/ptftests/py3/copp_tests.py:267:121: E501 line too long (128 > 120 characters) ansible/roles/test/files/ptftests/py3/copp_tests.py:268:21: E127 continuation line over-indented for visual indent ansible/roles/test/files/ptftests/py3/copp_tests.py:278:21: E127 continuation line over-indented for visual indent ansible/roles/test/files/ptftests/py3/copp_tests.py:540:121: E501 line too long (128 > 120 characters) ansible/roles/test/files/ptftests/py3/copp_tests.py:541:21: E127 continuation line over-indented for visual indent ansible/roles/test/files/ptftests/py3/copp_tests.py:551:21: E127 continuation line over-indented for visual indent ansible/roles/test/files/ptftests/py3/copp_tests.py:561:121: E501 line too long (129 > 120 characters) ansible/roles/test/files/ptftests/py3/copp_tests.py:562:121: E501 line too long (131 > 120 characters) flake8...............................................(no files to check)Skipped check conditional mark sort..............................................Passed

To run the pre-commit checks locally, you can follow below steps:

Ensure that default python is python3. In sonic-mgmt docker container, default python is python2. You can run
the check by activating the python3 virtual environment in sonic-mgmt docker container or outside of sonic-mgmt
docker container.
Ensure that the pre-commit package is installed:

sudo pip install pre-commit

Go to repository root folder
Install the pre-commit hooks:

pre-commit install

Use pre-commit to check staged file:

pre-commit

Alternatively, you can check committed files using:

pre-commit run --from-ref <commit_id> --to-ref <commit_id>

Signed-off-by: Prabhat Aravind <paravind@microsoft.com>

ZhaohuiS

LGTM

prabhataravind · 2024-07-03T02:26:56Z

/azpw run

prabhataravind · 2024-07-23T17:31:43Z

@StormLiangMS, could you please help cherry-pick to 202305 as well when ready?

prabhataravind · 2024-07-30T20:39:42Z

@StormLiangMS, could you please help cherry-pick to 202305 as well when ready?

@ZhaohuiS for viz

What is the motivation for this PR? Recently, a change was made in the test_policer testcase in copp_tests.py to retain the default value of cir/cbs for queue4_group3 (default value for mgmt is 300) instead of changing it to 600 on the DUT during the testcase run. The PR for this change is here - #12836. For marvell based platforms like Nokia-7215-T1 and Nokia-7215-A1, the cir/cbs values are supported in steps of 125. Therefore, a value of 300 in the copp_cfg.json will set it to 250 internally since 300 is not in steps of 125. This was confirmed by Marvell - "Per talk, the policer/ traffic metering can work in packet per-second mode. The granularity is in step of 125 pps. So it’s 125, 250 …etc Minimum is 125." The PPS_LIMIT_MIN and PPS_LIMIT_MAX is therefore set in the testcase to 270,390 respectively which is completely out of range and causes this testcase to fail. Therefore, this PR sets cir/cbs to 250 for Marvell based platforms. How did you do it? Added a platform specific check in copp_tests.py to change the PPS_LIMIT to 250 for Nokia platforms. How did you verify/test it? Ran test_policer testcase for DHCP, DHCP6, LLDP and UDLD. Verified that the testcase passes.

What is the motivation for this PR? Recently, a change was made in the test_policer testcase in copp_tests.py to retain the default value of cir/cbs for queue4_group3 (default value for mgmt is 300) instead of changing it to 600 on the DUT during the testcase run. The PR for this change is here - sonic-net#12836. For marvell based platforms like Nokia-7215-T1 and Nokia-7215-A1, the cir/cbs values are supported in steps of 125. Therefore, a value of 300 in the copp_cfg.json will set it to 250 internally since 300 is not in steps of 125. This was confirmed by Marvell - "Per talk, the policer/ traffic metering can work in packet per-second mode. The granularity is in step of 125 pps. So it’s 125, 250 …etc Minimum is 125." The PPS_LIMIT_MIN and PPS_LIMIT_MAX is therefore set in the testcase to 270,390 respectively which is completely out of range and causes this testcase to fail. Therefore, this PR sets cir/cbs to 250 for Marvell based platforms. How did you do it? Added a platform specific check in copp_tests.py to change the PPS_LIMIT to 250 for Nokia platforms. How did you verify/test it? Ran test_policer testcase for DHCP, DHCP6, LLDP and UDLD. Verified that the testcase passes.

What is the motivation for this PR? Recently, a change was made in the test_policer testcase in copp_tests.py to retain the default value of cir/cbs for queue4_group3 (default value for mgmt is 300) instead of changing it to 600 on the DUT during the testcase run. The PR for this change is here - #12836. For marvell based platforms like Nokia-7215-T1 and Nokia-7215-A1, the cir/cbs values are supported in steps of 125. Therefore, a value of 300 in the copp_cfg.json will set it to 250 internally since 300 is not in steps of 125. This was confirmed by Marvell - "Per talk, the policer/ traffic metering can work in packet per-second mode. The granularity is in step of 125 pps. So it’s 125, 250 …etc Minimum is 125." The PPS_LIMIT_MIN and PPS_LIMIT_MAX is therefore set in the testcase to 270,390 respectively which is completely out of range and causes this testcase to fail. Therefore, this PR sets cir/cbs to 250 for Marvell based platforms. How did you do it? Added a platform specific check in copp_tests.py to change the PPS_LIMIT to 250 for Nokia platforms. How did you verify/test it? Ran test_policer testcase for DHCP, DHCP6, LLDP and UDLD. Verified that the testcase passes.

What is the motivation for this PR? Recently, a change was made in the test_policer testcase in copp_tests.py to retain the default value of cir/cbs for queue4_group3 (default value for mgmt is 300) instead of changing it to 600 on the DUT during the testcase run. The PR for this change is here - sonic-net#12836. For marvell based platforms like Nokia-7215-T1 and Nokia-7215-A1, the cir/cbs values are supported in steps of 125. Therefore, a value of 300 in the copp_cfg.json will set it to 250 internally since 300 is not in steps of 125. This was confirmed by Marvell - "Per talk, the policer/ traffic metering can work in packet per-second mode. The granularity is in step of 125 pps. So it’s 125, 250 …etc Minimum is 125." The PPS_LIMIT_MIN and PPS_LIMIT_MAX is therefore set in the testcase to 270,390 respectively which is completely out of range and causes this testcase to fail. Therefore, this PR sets cir/cbs to 250 for Marvell based platforms. How did you do it? Added a platform specific check in copp_tests.py to change the PPS_LIMIT to 250 for Nokia platforms. How did you verify/test it? Ran test_policer testcase for DHCP, DHCP6, LLDP and UDLD. Verified that the testcase passes.

What is the motivation for this PR? Recently, a change was made in the test_policer testcase in copp_tests.py to retain the default value of cir/cbs for queue4_group3 (default value for mgmt is 300) instead of changing it to 600 on the DUT during the testcase run. The PR for this change is here - #12836. For marvell based platforms like Nokia-7215-T1 and Nokia-7215-A1, the cir/cbs values are supported in steps of 125. Therefore, a value of 300 in the copp_cfg.json will set it to 250 internally since 300 is not in steps of 125. This was confirmed by Marvell - "Per talk, the policer/ traffic metering can work in packet per-second mode. The granularity is in step of 125 pps. So it’s 125, 250 …etc Minimum is 125." The PPS_LIMIT_MIN and PPS_LIMIT_MAX is therefore set in the testcase to 270,390 respectively which is completely out of range and causes this testcase to fail. Therefore, this PR sets cir/cbs to 250 for Marvell based platforms. How did you do it? Added a platform specific check in copp_tests.py to change the PPS_LIMIT to 250 for Nokia platforms. How did you verify/test it? Ran test_policer testcase for DHCP, DHCP6, LLDP and UDLD. Verified that the testcase passes.

This PR does the following: Enhance copp test cases so that they pass consistently on Broadcom platforms. For Broadcom platforms, when BGP and IP2ME traps are removed, BGP packets hit the default trap group, so a new DefaultPolicy is introduced in check_constraints specifically for Broadcom ASIC types. The test logic for non-Broadcom platforms is left unchanged. A necessary side change of this is that the CIR for default trap needs to be changed to a value other than 600 only for the test. This is reverted back at the end of the test. Remove xfail for copp tests on broadcom platforms Skip updating default sonic config for queue4_group3 in scripts/update_copp_config.py as the new rate-limit for this copp group is lower than the default value of 600 PPS used by copp tests. This value is 300PPS for Mgmt devices and 100 PPS for other devices. The constraint checks for protocols that map to queue4_group3 are also changed accordingly in ansible/roles/test/files/ptftests/py3/copp_tests.py Summary: Fixes # 27262099 What is the motivation for this PR? When BGP and IP2ME traps are removed, BGP packets hit the default trap group on broadcom platforms and trap to CPU queue0. This change modifies copp test to verify this behavior. How did you do it? By changing the rate limit used in the test for default trap group, it is easy to verify that packets are hitting that trap group. If all trap groups use the same rate limit of 600 pps as is done currently, it is rather difficult to identify which trap group got hit. How did you verify/test it? By running tests locally and using azure pipeline

mssonicbld · 2024-08-28T04:19:27Z

Cherry-pick PR to 202305: #14290

This PR does the following: Enhance copp test cases so that they pass consistently on Broadcom platforms. For Broadcom platforms, when BGP and IP2ME traps are removed, BGP packets hit the default trap group, so a new DefaultPolicy is introduced in check_constraints specifically for Broadcom ASIC types. The test logic for non-Broadcom platforms is left unchanged. A necessary side change of this is that the CIR for default trap needs to be changed to a value other than 600 only for the test. This is reverted back at the end of the test. Remove xfail for copp tests on broadcom platforms Skip updating default sonic config for queue4_group3 in scripts/update_copp_config.py as the new rate-limit for this copp group is lower than the default value of 600 PPS used by copp tests. This value is 300PPS for Mgmt devices and 100 PPS for other devices. The constraint checks for protocols that map to queue4_group3 are also changed accordingly in ansible/roles/test/files/ptftests/py3/copp_tests.py Summary: Fixes # 27262099 What is the motivation for this PR? When BGP and IP2ME traps are removed, BGP packets hit the default trap group on broadcom platforms and trap to CPU queue0. This change modifies copp test to verify this behavior. How did you do it? By changing the rate limit used in the test for default trap group, it is easy to verify that packets are hitting that trap group. If all trap groups use the same rate limit of 600 pps as is done currently, it is rather difficult to identify which trap group got hit. How did you verify/test it? By running tests locally and using azure pipeline

Upstream PR sonic-net#12836 changed the copp policer limit for some traffic classes from 300 to 100, for all DUTs except M0. Pkz should be included in their M0 list as well (from testing applies to mx too)

What is the motivation for this PR? Recently, a change was made in the test_policer testcase in copp_tests.py to retain the default value of cir/cbs for queue4_group3 (default value for mgmt is 300) instead of changing it to 600 on the DUT during the testcase run. The PR for this change is here - sonic-net#12836. For marvell based platforms like Nokia-7215-T1 and Nokia-7215-A1, the cir/cbs values are supported in steps of 125. Therefore, a value of 300 in the copp_cfg.json will set it to 250 internally since 300 is not in steps of 125. This was confirmed by Marvell - "Per talk, the policer/ traffic metering can work in packet per-second mode. The granularity is in step of 125 pps. So it’s 125, 250 …etc Minimum is 125." The PPS_LIMIT_MIN and PPS_LIMIT_MAX is therefore set in the testcase to 270,390 respectively which is completely out of range and causes this testcase to fail. Therefore, this PR sets cir/cbs to 250 for Marvell based platforms. How did you do it? Added a platform specific check in copp_tests.py to change the PPS_LIMIT to 250 for Nokia platforms. How did you verify/test it? Ran test_policer testcase for DHCP, DHCP6, LLDP and UDLD. Verified that the testcase passes.

prabhataravind force-pushed the paravind/copp branch from a384552 to fab5392 Compare June 24, 2024 23:09

prabhataravind changed the title ~~[tests/copp]: Fix copp tests to address failures on broadcom platforms~~ [tests/copp]: Fix copp tests Jun 24, 2024

prabhataravind force-pushed the paravind/copp branch from fab5392 to 3dab091 Compare June 24, 2024 23:31

prabhataravind added 2 commits June 24, 2024 23:44

Fix copp tests for broadcom platforms

4ab8edd

Signed-off-by: Prabhat Aravind <paravind@microsoft.com>

Revert "xfail copp for broadcom (sonic-net#12026)"

742787d

This reverts commit 31101a5.

prabhataravind force-pushed the paravind/copp branch from 3dab091 to 742787d Compare June 24, 2024 23:44

Merge branch 'sonic-net:master' into paravind/copp

7a932d9

prabhataravind marked this pull request as ready for review June 26, 2024 03:52

prabhataravind requested review from StormLiangMS and prsunny June 26, 2024 03:52

StormLiangMS requested a review from ZhaohuiS June 27, 2024 08:42

prsunny previously approved these changes Jun 28, 2024

View reviewed changes

ZhaohuiS reviewed Jun 29, 2024

View reviewed changes

ansible/roles/test/files/ptftests/py3/copp_tests.py Show resolved Hide resolved

ZhaohuiS reviewed Jun 29, 2024

View reviewed changes

ansible/roles/test/files/ptftests/py3/copp_tests.py Outdated Show resolved Hide resolved

prabhataravind dismissed prsunny’s stale review via 04b3be6 July 2, 2024 02:08

prabhataravind requested review from ZhaohuiS and prsunny July 2, 2024 02:11

ZhaohuiS closed this Jul 2, 2024

ZhaohuiS reopened this Jul 2, 2024

Add more verbose comments for assertion failures

46d2d78

Signed-off-by: Prabhat Aravind <paravind@microsoft.com>

prabhataravind force-pushed the paravind/copp branch from 04b3be6 to 46d2d78 Compare July 2, 2024 16:40

Merge branch 'sonic-net:master' into paravind/copp

7e9df13

ZhaohuiS approved these changes Jul 3, 2024

View reviewed changes

mssonicbld added Included in 202311 branch and removed Created PR to 202405 branch Created PR to 202311 branch labels Jul 22, 2024

bingwang-ms mentioned this pull request Jul 24, 2024

[Bug]: test_copp test_add_new_trap and test_remove_trap failed on broadcom platform #13560

Open

prabhataravind added the Request for 202305 branch label Jul 30, 2024

tudupa mentioned this pull request Aug 5, 2024

Fixed copp/test_policer testcase for DHCP, DHCP6, LLDP and UDLD scenarios for marvell based platforms #13989

Merged

8 tasks

mssonicbld mentioned this pull request Aug 14, 2024

[action] [PR:13989] Fixed copp/test_policer testcase for DHCP, DHCP6, LLDP and UDLD scenarios for marvell based platforms #14114

Merged

8 tasks

mssonicbld mentioned this pull request Aug 15, 2024

[action] [PR:13989] Fixed copp/test_policer testcase for DHCP, DHCP6, LLDP and UDLD scenarios for marvell based platforms #14134

Merged

8 tasks

veronica-arista mentioned this pull request Aug 23, 2024

Xfail copp add/remove trap tests on 7050CX3 SKUs #14219

Merged

8 tasks

StormLiangMS added the Approved for 202305 branch label Aug 28, 2024

mssonicbld added the Created PR to 202305 branch label Aug 28, 2024

mssonicbld mentioned this pull request Aug 28, 2024

[action] [PR:12836] [tests/copp]: Fix copp tests #14290

Merged

8 tasks

mssonicbld added Included in 202305 branch and removed Created PR to 202305 branch labels Aug 28, 2024

veronica-arista mentioned this pull request Sep 5, 2024

Add Arista M0 devices to copp_tests M0 device list #14443

Closed

8 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[tests/copp]: Fix copp tests #12836

[tests/copp]: Fix copp tests #12836

prabhataravind commented May 13, 2024 •

edited

Loading

mssonicbld commented May 13, 2024

mssonicbld commented Jun 24, 2024

mssonicbld commented Jun 24, 2024

prsunny left a comment

mssonicbld commented Jul 2, 2024

ZhaohuiS commented Jul 2, 2024

mssonicbld commented Jul 2, 2024

ZhaohuiS left a comment

prabhataravind commented Jul 3, 2024

prabhataravind commented Jul 23, 2024

prabhataravind commented Jul 30, 2024

mssonicbld commented Aug 28, 2024

[tests/copp]: Fix copp tests #12836

[tests/copp]: Fix copp tests #12836

Conversation

prabhataravind commented May 13, 2024 • edited Loading

Description of PR

Type of change

Back port request

Approach

What is the motivation for this PR?

How did you do it?

How did you verify/test it?

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

mssonicbld commented May 13, 2024

mssonicbld commented Jun 24, 2024

mssonicbld commented Jun 24, 2024

prsunny left a comment

Choose a reason for hiding this comment

mssonicbld commented Jul 2, 2024

ZhaohuiS commented Jul 2, 2024

mssonicbld commented Jul 2, 2024

ZhaohuiS left a comment

Choose a reason for hiding this comment

prabhataravind commented Jul 3, 2024

prabhataravind commented Jul 23, 2024

prabhataravind commented Jul 30, 2024

mssonicbld commented Aug 28, 2024

prabhataravind commented May 13, 2024 •

edited

Loading