From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, dukaix.yuan@intel.com
Subject: [dts-test-report] |SUCCESS| pw(121349) sid(26259) job(DTS_AUTO_2164) [V1] tests/loopback multi paths port restart: optimize the script to be consistent with test plan
Date: 23 Dec 2022 02:10:32 -0800 [thread overview]
Message-ID: <510f81$lf712j@fmsmga004-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3310 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/121349
Subject: [V1] tests/loopback multi paths port restart: optimize the script to be consistent with test plan
_Testing OK_
Diff:
tests/TestSuite_loopback_multi_paths_port_restart.py
DPDK:
commit 373f4c7de8ff350548cacc3d56e788461677f2c7
Author: David Marchand <david.marchand@redhat.com>
Date: Tue Dec 13 16:07:10 2022 +0100
Comment: ci: drop Travis configuration
DTS:
commit 6640ecb3ebc5347139df2530bdfd2fa5421b6a47
Author: Lingli Chen <linglix.chen@intel.com>
Date: Thu Dec 15 01:42:04 2022 -0500
Comment: tests/rss_to_rte_flow: remove --pkt-filter-mode sync dpdk change
Test environment and result as below:
+-----------------------------------+----------+--------------------------------+---------------------------------+
| suits | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+-----------------------------------+----------+--------------------------------+---------------------------------+
| loopback_multi_paths_port_restart | Virtio | run | not run |
+-----------------------------------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/db4900e6742b43728db10cfade66a06c
#1: UB2004-64+216_fortville_spirit
OS: Ubuntu 22.10
Kernel: 6.0.7-060007-generic
CPU: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
GCC: gcc (Ubuntu 12.2.0-3ubuntu1) 12.2.0
Clang: NA
Status: SUCCESS
Catogory: Virtio
Target: x86_64-native-linuxapp-gcc
with_patch Total/Pass/Fail/Blocked/NA: 10/10/0/0/0
Detail test results:
+-------------------------------------------------------------------------------------------------+------------+
| suit/case | with_patch |
+-------------------------------------------------------------------------------------------------+------------+
| loopback_multi_paths_port_restart/test_lookback_test_with_packed_ring_inorder_mergeable_path | passed |
| loopback_multi_paths_port_restart/test_lookback_test_with_packed_ring_inorder_nonmergeable_path | passed |
| loopback_multi_paths_port_restart/test_lookback_test_with_packed_ring_vectorized_path | passed |
| loopback_multi_paths_port_restart/test_lookback_test_with_split_ring_inorder_mergeable_path | passed |
| loopback_multi_paths_port_restart/test_lookback_test_with_split_ring_inorder_nonmergeable_path | passed |
| loopback_multi_paths_port_restart/test_lookback_test_with_split_ring_mergeable_path | passed |
| loopback_multi_paths_port_restart/test_lookback_test_with_split_ring_nonmergeable_path | passed |
| loopback_multi_paths_port_restart/test_loopback_test_with_packed_ring_mergeable_path | passed |
| loopback_multi_paths_port_restart/test_loopback_test_with_packed_ring_nonmergeable_path | passed |
| loopback_multi_paths_port_restart/test_loopback_test_with_split_ring_vector_rx_path | passed |
+-------------------------------------------------------------------------------------------------+------------+
DPDK STV team
next reply other threads:[~2022-12-23 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 10:10 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-23 9:53 sys_stv
2022-12-23 9:52 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='510f81$lf712j@fmsmga004-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=dukaix.yuan@intel.com \
--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).