From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, akihiko.odaki@daynix.com
Subject: [dts-test-report] |SUCCESS| pw(126091-126097) sid(27720) job(DTS_AUTO_2569) [7/7] tests/ip_pipeline: Use common tcpdump methods
Date: 14 Apr 2023 07:13:31 -0700 [thread overview]
Message-ID: <1c0cbc$lets7d@orsmga008-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5206 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/126097
Subject: [7/7] tests/ip_pipeline: Use common tcpdump methods
_Testing OK_
Diff:
requirements.txt
doc/dts_gsg/usr_guide/sys_reqs.rst
ci/dts_requirements.txt
framework/ssh_pexpect.py
framework/dut.py
nics/system_info.py
framework/packet.py
tests/TestSuite_ip_pipeline.py
DPDK:
commit 3b3fef9de22af80d173453ab65a80b01ce38cbfd
Author: Elena Agostini <eagostini@nvidia.com>
Date: Thu Apr 6 09:49:44 2023 +0000
Comment: net: fix return type of IPv4 L4 packet checksum
DTS:
commit 1c14b5d745a3fdc7271d7c18422ffdb06e8510b3
Author: Wei Ling <weix.ling@intel.com>
Date: Fri Mar 31 11:36:36 2023 +0800
Comment: tests/vhost_user_live_migration: add 2 testcase sync with testplan
Test environment and result as below:
+---------------------+----------+---------------------------------+--------------------------------+
| suits | category | UB2004-64+216_columbiaville_25g | UB2004-64+216_fortville_spirit |
+---------------------+----------+---------------------------------+--------------------------------+
| vf_to_vf_nic_bridge | NIC VF | not run | run |
| vf_smoke | NIC VF | not run | run |
| pf_smoke | NIC PF | not run | run |
| virtio_smoke | Virtio | not run | run |
| ice_rss_configure | CVL Only | run | not run |
+---------------------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/082aa9206e034785b68a5776dac62ad0
#1: UB2004-64+216_fortville_spirit
OS: Ubuntu 20.04.5 LTS
Kernel: 5.4.0-135-generic
CPU: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang: NA
Status: SUCCESS
Catogory: NIC PF
Target: x86_64-native-linuxapp-gcc
with_patch Total/Pass/Fail/Blocked/NA: 3/3/0/0/0
Detail test results:
+-------------------------------+------------+
| suit/case | with_patch |
+-------------------------------+------------+
| pf_smoke/test_pf_jumbo_frames | passed |
| pf_smoke/test_pf_rss | passed |
| pf_smoke/test_pf_tx_rx_queue | passed |
+-------------------------------+------------+
Status: SUCCESS
Catogory: NIC VF
Target: x86_64-native-linuxapp-gcc
with_patch Total/Pass/Fail/Blocked/NA: 6/6/0/0/0
Detail test results:
+-------------------------------------------------+------------+
| suit/case | with_patch |
+-------------------------------------------------+------------+
| vf_smoke/test_vf_jumbo_frames | passed |
| vf_smoke/test_vf_rss | passed |
| vf_smoke/test_vf_tx_rx_queue | passed |
| vf_to_vf_nic_bridge/test_2vf_d2d_testpmd_stream | passed |
| vf_to_vf_nic_bridge/test_2vf_d2k_testpmd_stream | passed |
| vf_to_vf_nic_bridge/test_2vf_k2d_scapy_stream | passed |
+-------------------------------------------------+------------+
Status: SUCCESS
Catogory: Virtio
Target: x86_64-native-linuxapp-gcc
with_patch Total/Pass/Fail/Blocked/NA: 2/2/0/0/0
Detail test results:
+-----------------------------------+------------+
| suit/case | with_patch |
+-----------------------------------+------------+
| virtio_smoke/test_virtio_loopback | passed |
| virtio_smoke/test_virtio_pvp | passed |
+-----------------------------------+------------+
#2: UB2004-64+216_columbiaville_25g
OS: Ubuntu 20.04.5 LTS
Kernel: 5.4.0-135-generic
CPU: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang: NA
Status: SUCCESS
Catogory: CVL Only
Target: x86_64-native-linuxapp-gcc
with_patch Total/Pass/Fail/Blocked/NA: 11/11/0/0/0
Detail test results:
+--------------------------------------------------------+------------+
| suit/case | with_patch |
+--------------------------------------------------------+------------+
| ice_rss_configure/test_command_line_option_rss_default | passed |
| ice_rss_configure/test_command_line_option_rss_disable | passed |
| ice_rss_configure/test_command_line_option_rss_ip | passed |
| ice_rss_configure/test_command_line_option_rss_udp | passed |
| ice_rss_configure/test_rss_configure_to_all | passed |
| ice_rss_configure/test_rss_configure_to_default | passed |
| ice_rss_configure/test_rss_configure_to_ip | passed |
| ice_rss_configure/test_rss_configure_to_none | passed |
| ice_rss_configure/test_rss_configure_to_sctp | passed |
| ice_rss_configure/test_rss_configure_to_tcp | passed |
| ice_rss_configure/test_rss_configure_to_udp | passed |
+--------------------------------------------------------+------------+
DPDK STV team
next reply other threads:[~2023-04-14 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 14:13 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-14 13:39 sys_stv
2023-04-14 13:38 sys_stv
2023-04-14 13:37 sys_stv
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='1c0cbc$lets7d@orsmga008-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=akihiko.odaki@daynix.com \
--cc=dts-test-report@dpdk.org \
--cc=test-report@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).