From: sys_stv@intel.com
To: test-report@dpdk.org, ciara.loftus@intel.com
Cc: daxuex.gao@intel.com
Subject: |FAILURE|dpdk|f3878b615e| intel-Functional
Date: 01 Oct 2025 09:18:05 -0700 [thread overview]
Message-ID: <7c7456$5a5gr6@fmviesa007-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4638 bytes --]
Test-Label: intel-Functional
Test-Status: FAILURE
_Functional issues_
DPDK git repo: dpdk
commit f3878b615e69a12087a6c5d212723478cfc79c31
Author: Ciara Loftus <ciara.loftus@intel.com>
Date: Tue Sep 16 14:21:08 2025 +0000
doc: fix feature list of iavf driver
The iavf PMD does not report the speed capabilities that the device is
capable of in the speed_capa field of the rte_eth_dev_info struct. The
documentation incorrectly stated this feature as supported. Fix this.
The free tx mbuf on demand feature has been supported since commit
86e44244f95c ("net/iavf: cleanup Tx buffers"). Update the list of
supported features to reflect this.
The burst mode info feature has been supported since commit 0d5a856f5be9
("net/iavf: support Rx/Tx burst mode info"). Update the list of
supported features to reflect this.
The extended statistics feature has been implemented since commit
d38a06bf4367 ("net/iavf: add extended stats"). Update the list of
supported features to reflect this.
Fixes: 48de41ca11f0 ("net/avf: enable link status update")
Fixes: 86e44244f95c ("net/iavf: cleanup Tx buffers")
Fixes: 0d5a856f5be9 ("net/iavf: support Rx/Tx burst mode info")
Fixes: d38a06bf4367 ("net/iavf: add extended stats")
Cc: stable@dpdk.org
Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Smoke-Testing Summary : 31 Case Done, 12 Successful, 19 Failures
OS : Ubuntu 22.04.2 LTS
Kernel : 5.15.0-60-generic
GCC : 11.3.0-1ubuntu1~22.04
NIC : Ethernet Controller XL710 for 40GbE QSFP+
Target : x86_64-native-linuxapp-gcc
Test result details:
+-----------------+---------------------------------------------------+--------+
| suite | case | status |
+-----------------+---------------------------------------------------+--------+
| checksum_offload| test_checksum_offload_with_vlan | FAILED |
| checksum_offload| test_do_not_insert_checksum_on_the_transmit_packet| FAILED |
| checksum_offload| test_hardware_checksum_check_ip_rx | FAILED |
| checksum_offload| test_hardware_checksum_check_ip_tx | FAILED |
| checksum_offload| test_hardware_checksum_check_l4_rx | FAILED |
| checksum_offload| test_hardware_checksum_check_l4_tx | FAILED |
| checksum_offload| test_insert_checksum_on_the_transmit_packet | FAILED |
| checksum_offload| test_rx_checksum_valid_flags | FAILED |
| dual_vlan | test_dual_vlan_priority_rxtx | blocked|
| dual_vlan | test_vlan_filter_config | blocked|
| dual_vlan | test_vlan_filter_table | blocked|
| dual_vlan | test_vlan_insert_config | blocked|
| dual_vlan | test_vlan_random_test | blocked|
| dual_vlan | test_vlan_strip_config | blocked|
| dual_vlan | test_vlan_stripq_config | blocked|
| dual_vlan | test_vlan_synthetic_test | blocked|
| dual_vlan | test_vlan_tpid_config | blocked|
| jumboframes | test_jumboframes_bigger_jumbo | FAILED |
| jumboframes | test_jumboframes_jumbo_jumbo | FAILED |
| jumboframes | test_jumboframes_jumbo_nojumbo | FAILED |
| jumboframes | test_jumboframes_normal_jumbo | FAILED |
| jumboframes | test_jumboframes_normal_nojumbo | FAILED |
| rxtx_offload | test_rxoffload_port_all | FAILED |
| rxtx_offload | test_rxoffload_port_cmdline | FAILED |
| rxtx_offload | test_txoffload_port | FAILED |
| rxtx_offload | test_txoffload_port_all | FAILED |
| rxtx_offload | test_txoffload_port_checksum | FAILED |
| rxtx_offload | test_txoffload_port_cmdline | FAILED |
| rxtx_offload | test_rxoffload_queue | n/a |
| rxtx_offload | test_txoffload_port_multi_segs | n/a |
| rxtx_offload | test_txoffload_queue | n/a |
+-----------------+---------------------------------------------------+--------+
DPDK STV team
reply other threads:[~2025-10-01 16:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='7c7456$5a5gr6@fmviesa007-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=ciara.loftus@intel.com \
--cc=daxuex.gao@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).