Adding tgen pytest mark to couple of pfc snappi-tests.#19027
Adding tgen pytest mark to couple of pfc snappi-tests.#19027yejianquan merged 2 commits intosonic-net:masterfrom
Conversation
adding tgen pytest mark to the test case
adding tgen pytest mark to the test case
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
AzDevOps@e1a1448fa9a4:~/sonic-mgmt/tests$ python3 -m pytest --inventory ../ansible/snappi-sonic --host-pattern sonic-s6100-dut1 --testbed vms-snappi-sonic --testbed_file ../ansible/testbed.yaml --show-capture=stdout --log-cli-level info --showlocals -ra --allow_recover --skip_sanity --disable_loganalyzer --topology tgen snappi_tests/pfc/test_m2o_fluctuating_lossless.py ---------------------------------------------------------------------------------------------- live log sessionstart ---------------------------------------------------------------------------------------------- 05:55:23 conftest.pytest_sessionstart L0491 INFO | Added /var/AzDevOps/sonic-mgmt/tests/common/sai_validation/generated to sys.path snappi_tests/pfc/test_m2o_fluctuating_lossless.py::test_m2o_fluctuating_lossless[tgen_port_info0]
================================================================================================ warnings summary ================================================================================================= ../../../../usr/local/lib/python3.8/dist-packages/_pytest/config/init.py:755 ../../../../usr/local/lib/python3.8/dist-packages/_pytest/config/init.py:755 ../../../../usr/local/lib/python3.8/dist-packages/_pytest/config/init.py:755 ../../../../usr/local/lib/python3.8/dist-packages/_pytest/config/init.py:755 ../../../../usr/local/lib/python3.8/dist-packages/_pytest/config/init.py:755 ../../../../usr/local/lib/python3.8/dist-packages/paramiko/transport.py:236 ../../../../usr/local/lib/python3.8/dist-packages/scapy/layers/ipsec.py:471 ../../../../usr/local/lib/python3.8/dist-packages/scapy/layers/ipsec.py:485 snappi_tests/pfc/test_m2o_fluctuating_lossless.py::test_m2o_fluctuating_lossless[tgen_port_info0] -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html ---------------------------- live log sessionstart ----------------------------- 19:20:30 conftest.pytest_sessionstart L0491 INFO | Added /var/AzDevOps/sonic-mgmt/tests/common/sai_validation/generated to sys.path snappi_tests/pfc/test_m2o_oversubscribe_lossy.py::test_m2o_oversubscribe_lossy[400.0-single_linecard_single_asic] =============================== warnings summary =============================== ../../../../usr/local/lib/python3.8/dist-packages/_pytest/config/init.py:755 ../../../../usr/local/lib/python3.8/dist-packages/_pytest/config/init.py:755 ../../../../usr/local/lib/python3.8/dist-packages/_pytest/config/init.py:755 ../../../../usr/local/lib/python3.8/dist-packages/_pytest/config/init.py:755 ../../../../usr/local/lib/python3.8/dist-packages/_pytest/config/init.py:755 ../../../../usr/local/lib/python3.8/dist-packages/paramiko/transport.py:236 ../../../../usr/local/lib/python3.8/dist-packages/scapy/layers/ipsec.py:471 ../../../../usr/local/lib/python3.8/dist-packages/scapy/layers/ipsec.py:485 snappi_tests/pfc/test_m2o_oversubscribe_lossy.py::test_m2o_oversubscribe_lossy[400.0-single_linecard_single_asic] -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html |
Description of PR Summary: Added tgen in addition to multidut-tgen Approach What is the motivation for this PR? to add missing coverage on tgen How did you do it? Added tgen pytest mark How did you verify/test it? Ran on a single dut switch co-authorized by: [email protected]
|
Cherry-pick PR to 202505: #19204 |
Description of PR Summary: Added tgen in addition to multidut-tgen Approach What is the motivation for this PR? to add missing coverage on tgen How did you do it? Added tgen pytest mark How did you verify/test it? Ran on a single dut switch co-authorized by: [email protected]
Description of PR Summary: Added tgen in addition to multidut-tgen Approach What is the motivation for this PR? to add missing coverage on tgen How did you do it? Added tgen pytest mark How did you verify/test it? Ran on a single dut switch co-authorized by: [email protected]
Description of PR Summary: Added tgen in addition to multidut-tgen Approach What is the motivation for this PR? to add missing coverage on tgen How did you do it? Added tgen pytest mark How did you verify/test it? Ran on a single dut switch co-authorized by: [email protected]
Description of PR Summary: Added tgen in addition to multidut-tgen Approach What is the motivation for this PR? to add missing coverage on tgen How did you do it? Added tgen pytest mark How did you verify/test it? Ran on a single dut switch co-authorized by: [email protected] Signed-off-by: opcoder0 <[email protected]>
Description of PR Summary: Added tgen in addition to multidut-tgen Approach What is the motivation for this PR? to add missing coverage on tgen How did you do it? Added tgen pytest mark How did you verify/test it? Ran on a single dut switch co-authorized by: [email protected] Signed-off-by: Guy Shemesh <[email protected]>
Description of PR Summary: Added tgen in addition to multidut-tgen Approach What is the motivation for this PR? to add missing coverage on tgen How did you do it? Added tgen pytest mark How did you verify/test it? Ran on a single dut switch co-authorized by: [email protected] Signed-off-by: Aharon Malkin <[email protected]>
Description of PR Summary: Added tgen in addition to multidut-tgen Approach What is the motivation for this PR? to add missing coverage on tgen How did you do it? Added tgen pytest mark How did you verify/test it? Ran on a single dut switch co-authorized by: [email protected] Signed-off-by: Guy Shemesh <[email protected]>
Description of PR Summary: Added tgen in addition to multidut-tgen Approach What is the motivation for this PR? to add missing coverage on tgen How did you do it? Added tgen pytest mark How did you verify/test it? Ran on a single dut switch co-authorized by: [email protected]
Description of PR Summary: Added tgen in addition to multidut-tgen Approach What is the motivation for this PR? to add missing coverage on tgen How did you do it? Added tgen pytest mark How did you verify/test it? Ran on a single dut switch co-authorized by: [email protected] Signed-off-by: Guy Shemesh <[email protected]>
Description of PR Summary: Added tgen in addition to multidut-tgen Approach What is the motivation for this PR? to add missing coverage on tgen How did you do it? Added tgen pytest mark How did you verify/test it? Ran on a single dut switch co-authorized by: [email protected] Signed-off-by: Yael Tzur <[email protected]>
Description of PR
Summary:
Added tgen in addition to multidut-tgen
Type of change
Back port request
Approach
What is the motivation for this PR?
to add missing coverage on tgen
How did you do it?
Added tgen pytest mark
How did you verify/test it?
Ran on a single dut switch
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation