From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, weiyuanx.li@intel.com
Subject: [dts-test-report] |SUCCESS| pw(122995-122996) sid(26778) job(DTS_AUTO_2384) [V1, 2/2] tests/vf_vlan: optimize script test step rx does not support IXGBE
Date: 05 Feb 2023 21:58:05 -0800 [thread overview]
Message-ID: <17e395$mg52a5@fmsmga003-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1943 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/122996
Subject: [V1,2/2] tests/vf_vlan: optimize script test step rx does not support IXGBE
_Testing OK_
Diff:
test_plans/vf_vlan_test_plan.rst
tests/TestSuite_vf_vlan.py
DPDK:
commit a27bb7bc786dee5dcc8b7ee03942f85173620314
Author: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Date: Thu Jan 26 14:12:56 2023 +0000
Comment: examples/pipeline: add IPsec example
DTS:
commit 11b6c1ea068db82d415f2ae0c042963d956daf69
Author: Lijuan Tu <lijuan.tu@intel.com>
Date: Thu Feb 2 13:53:18 2023 +0800
Comment: version: 23.03-rc0
Test environment and result as below:
+---------+----------+--------------------------------+---------------------------------+
| suits | category | UB2004-64+216_fortville_spirit | UB2004-64+216_columbiaville_25g |
+---------+----------+--------------------------------+---------------------------------+
| vf_vlan | NIC VF | run | not run |
+---------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/c3f659746805448689283d889ab47763
#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 VF
Target: x86_64-native-linuxapp-gcc
with_patch Total/Pass/Fail/Blocked/NA: 5/5/0/0/0
Detail test results:
+----------------------------+------------+
| suit/case | with_patch |
+----------------------------+------------+
| vf_vlan/test_add_pvid_vf | passed |
| vf_vlan/test_pvid_vf_tx | passed |
| vf_vlan/test_vf_vlan_rx | passed |
| vf_vlan/test_vf_vlan_strip | passed |
| vf_vlan/test_vf_vlan_tx | passed |
+----------------------------+------------+
DPDK STV team
next reply other threads:[~2023-02-06 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 5:58 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-06 5:40 sys_stv
2023-02-06 5:39 sys_stv
2023-02-06 5:38 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='17e395$mg52a5@fmsmga003-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=test-report@dpdk.org \
--cc=weiyuanx.li@intel.com \
/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).