From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, ke1.xu@intel.com
Subject: [dts-test-report] |SUCCESS| pw(125411) sid(27492) job(DTS_AUTO_2512) [V3] tests/vf_vlan: Add avx512 support for vf vlan validation.
Date: 21 Mar 2023 23:40:19 -0700 [thread overview]
Message-ID: <90bd5b$k3s439@orsmga007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2264 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/125411
Subject: [V3] tests/vf_vlan: Add avx512 support for vf vlan validation.
_Testing OK_
Diff:
tests/TestSuite_vf_vlan.py
DPDK:
commit 1a80f6062cf74e4b689b8b9a4f905a24efec527a
Author: Joyce Kong <joyce.kong@arm.com>
Date: Tue Mar 21 09:44:33 2023 +0000
Comment: config/arm: support LDAPR on Neoverse N1
DTS:
commit 964b48e223f9f3d4f1fe60502f40be7f85a9f661
Author: Song Jiale <songx.jiale@intel.com>
Date: Mon Jan 16 15:00:02 2023 +0000
Comment: tests/shutdown_api: modify the command to adapt to the changes in ethtool
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/8957c6e5a6b240479e86b071c11a89c8
#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: 10/10/0/0/0
Detail test results:
+-----------------------------------+------------+
| suit/case | with_patch |
+-----------------------------------+------------+
| vf_vlan/test_add_pvid_vf | passed |
| vf_vlan/test_add_pvid_vf_avx512 | passed |
| vf_vlan/test_pvid_vf_tx | passed |
| vf_vlan/test_pvid_vf_tx_avx512 | passed |
| vf_vlan/test_vf_vlan_rx | passed |
| vf_vlan/test_vf_vlan_rx_avx512 | passed |
| vf_vlan/test_vf_vlan_strip | passed |
| vf_vlan/test_vf_vlan_strip_avx512 | passed |
| vf_vlan/test_vf_vlan_tx | passed |
| vf_vlan/test_vf_vlan_tx_avx512 | passed |
+-----------------------------------+------------+
DPDK STV team
next reply other threads:[~2023-03-22 6:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 6:40 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-22 6:15 sys_stv
2023-03-22 6:14 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='90bd5b$k3s439@orsmga007-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=ke1.xu@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).