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(123874-123878) sid(26999) job(DTS_AUTO_2414) [V4, 5/5] test_plans/vf_offload: add VLAN packets to test scope and improve vector path validating.
Date: 13 Feb 2023 23:14:56 -0800 [thread overview]
Message-ID: <1ac5b1$kr19ru@orsmga008-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4570 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/123878
Subject: [V4,5/5] test_plans/vf_offload: add VLAN packets to test scope and improve vector path validating.
_Testing OK_
Diff:
tests/TestSuite_vf_offload.py
test_plans/vf_offload_test_plan.rst
DPDK:
commit 39d469a7eb4f157923be73aea0b0cc1015860ca7
Author: Robin Jarry <rjarry@redhat.com>
Date: Thu Feb 9 10:43:54 2023 +0100
Comment: eal: add lcore usage telemetry endpoint
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_offload | NIC VF | run | not run |
+------------+----------+--------------------------------+---------------------------------+
Log path: /regression_dts/results/test/ebab1d337371478ca8aa8f0e15c866e3
#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: 35/20/0/0/15
Detail test results:
+------------------------------------------------------------+------------+
| suit/case | with_patch |
+------------------------------------------------------------+------------+
| vf_offload/test_checksum_offload_disable | passed |
| vf_offload/test_checksum_offload_disable_avx2 | passed |
| vf_offload/test_checksum_offload_disable_avx512 | passed |
| vf_offload/test_checksum_offload_disable_scalar | passed |
| vf_offload/test_checksum_offload_disable_sse | passed |
| vf_offload/test_checksum_offload_enable | passed |
| vf_offload/test_checksum_offload_enable_avx2 | passed |
| vf_offload/test_checksum_offload_enable_avx512 | passed |
| vf_offload/test_checksum_offload_enable_scalar | passed |
| vf_offload/test_checksum_offload_enable_sse | passed |
| vf_offload/test_checksum_offload_tunnel_enable | n/a |
| vf_offload/test_checksum_offload_tunnel_enable_avx2 | n/a |
| vf_offload/test_checksum_offload_tunnel_enable_avx512 | n/a |
| vf_offload/test_checksum_offload_tunnel_enable_scalar | n/a |
| vf_offload/test_checksum_offload_tunnel_enable_sse | n/a |
| vf_offload/test_checksum_offload_vlan_enable | passed |
| vf_offload/test_checksum_offload_vlan_enable_avx2 | passed |
| vf_offload/test_checksum_offload_vlan_enable_avx512 | passed |
| vf_offload/test_checksum_offload_vlan_enable_scalar | passed |
| vf_offload/test_checksum_offload_vlan_enable_sse | passed |
| vf_offload/test_checksum_offload_vlan_tunnel_enable | n/a |
| vf_offload/test_checksum_offload_vlan_tunnel_enable_avx2 | n/a |
| vf_offload/test_checksum_offload_vlan_tunnel_enable_avx512 | n/a |
| vf_offload/test_checksum_offload_vlan_tunnel_enable_scalar | n/a |
| vf_offload/test_checksum_offload_vlan_tunnel_enable_sse | n/a |
| vf_offload/test_tso | passed |
| vf_offload/test_tso_avx2 | passed |
| vf_offload/test_tso_avx512 | passed |
| vf_offload/test_tso_scalar | passed |
| vf_offload/test_tso_sse | passed |
| vf_offload/test_tso_tunnel | n/a |
| vf_offload/test_tso_tunnel_avx2 | n/a |
| vf_offload/test_tso_tunnel_avx512 | n/a |
| vf_offload/test_tso_tunnel_scalar | n/a |
| vf_offload/test_tso_tunnel_sse | n/a |
+------------------------------------------------------------+------------+
DPDK STV team
next reply other threads:[~2023-02-14 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 7:14 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-14 6:43 sys_stv
2023-02-14 6:42 sys_stv
2023-02-14 6:41 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='1ac5b1$kr19ru@orsmga008-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).