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(126085) sid(27718) job(DTS_AUTO_2567) tests/dual_vlan: Explicitly wait for tcpdump
Date: 14 Apr 2023 06:10:10 -0700 [thread overview]
Message-ID: <c279bf$mju03q@fmsmga004-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2165 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/126085
Subject: tests/dual_vlan: Explicitly wait for tcpdump
_Testing OK_
Diff:
tests/TestSuite_dual_vlan.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_fortville_spirit | UB2004-64+216_columbiaville_25g |
+-----------+----------+--------------------------------+---------------------------------+
| dual_vlan | NIC PF | run | not run |
+-----------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/ed8730a8dd6d4aeebd977ea868485c30
#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: 8/7/0/0/1
Detail test results:
+------------------------------------+------------+
| suit/case | with_patch |
+------------------------------------+------------+
| dual_vlan/test_vlan_filter_config | passed |
| dual_vlan/test_vlan_filter_table | passed |
| dual_vlan/test_vlan_insert_config | passed |
| dual_vlan/test_vlan_random_test | passed |
| dual_vlan/test_vlan_strip_config | passed |
| dual_vlan/test_vlan_stripq_config | n/a |
| dual_vlan/test_vlan_synthetic_test | passed |
| dual_vlan/test_vlan_tpid_config | passed |
+------------------------------------+------------+
DPDK STV team
next reply other threads:[~2023-04-14 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 13:10 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-14 13:00 sys_stv
2023-04-14 12:59 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='c279bf$mju03q@fmsmga004-auth.fm.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).