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(125137) sid(27399) job(DTS_AUTO_2489) [V1] tests/vf_offload: fix wrong value assigned for VxLAN packet under DCF.
Date: 16 Mar 2023 01:20:12 -0700 [thread overview]
Message-ID: <374626$jil1su@orsmga006-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4595 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: SUCCESS
http://dpdk.org/patch/125137
Subject: [V1] tests/vf_offload: fix wrong value assigned for VxLAN packet under DCF.
_Testing OK_
Diff:
tests/TestSuite_vf_offload.py
DPDK:
commit 8c9bfcb1553d756eb5392a56ac7813b3865c3ec7
Author: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Mon Mar 13 04:36:58 2023 -0700
Comment: mldev: remove weak symbols use in type conversions
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_columbiaville_25g | UB2004-64+216_fortville_spirit |
+------------+----------+---------------------------------+--------------------------------+
| vf_offload | NIC VF | not run | run |
+------------+----------+---------------------------------+--------------------------------+
Log path: /regression_dts/results/test/a64776c287da46bc913e0ea29ea60509
#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-03-16 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 8:20 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-16 7:48 sys_stv
2023-03-16 7:47 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='374626$jil1su@orsmga006-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).