From: "Bathija, Pravin" <Pravin.Bathija@dell.com>
To: fengchengwen <fengchengwen@huawei.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: FW: |Smoke |FAILURE| pw(158765-158768) sid(36689) job(PER_PATCH_BUILD17274-20251113210704) [v5,4/4] vhost_user: Function defs for add/rem mem regions
Date: Tue, 25 Nov 2025 07:23:52 +0000 [thread overview]
Message-ID: <SJ0PR19MB4606FAC1A477B65FC4AF1CEBF5D1A@SJ0PR19MB4606.namprd19.prod.outlook.com> (raw)
In-Reply-To: <553996$6i5mrh@smtpauth.intel.com>
Dear Fengcheng, Maxime,
When I look at the test results below, I see that one of the tests "test_checksum_offload_with_vlan" failed. However, when I navigate to the actual test results page - that same test shows passed. Could you please share your thoughts on this ?
https://mails.dpdk.org/archives/test-report/2025-November/931175.html
Also, any thoughts on when my code will be merged to mainline ?
Regards,
Pravin
Internal Use - Confidential
-----Original Message-----
From: sys_stv@intel.com <sys_stv@intel.com>
Sent: Thursday, November 13, 2025 9:48 AM
To: test-report@dpdk.org; Bathija, Pravin <Pravin.Bathija@dell.com>
Cc: daxuex.gao@intel.com
Subject: |Smoke |FAILURE| pw(158765-158768) sid(36689) job(PER_PATCH_BUILD17274-20251113210704) [v5,4/4] vhost_user: Function defs for add/rem mem regions
[EXTERNAL EMAIL]
Test-Label: intel-Functional
Test-Status: FAILURE
https://urldefense.com/v3/__http://dpdk.org/patch/158768__;!!LpKI!jCHbWxKxAWgIg6OQEvPP3-yCEWdKOlDUFrlDl-Njivh4rgNkJqRj9YFVVY9hRHocrV4lnvkjjvMMC85WVA$ [dpdk[.]org]
_Functional issues_
Submitter: Pravin M Bathija <pravin.bathija@dell.com>
Date: 2025-11-13 12:44:22
Branch : dpdk-next-virtio
CommitID: 6b37c26a95
Smoke-Testing Summary : 31 Case Done, 30 Successful, 1 Failures
OS : Ubuntu 24.04.3 LTS
Kernel : 6.8.0-71-generic
GCC : 13.3.0-6ubuntu2~24.04
NIC : Ethernet Controller XL710 for 40GbE QSFP+
Target : x86_64-native-linuxapp-gcc
Test result details:
+-----------------+---------------------------------------------------+-------+
| suite | case | status|
+-----------------+---------------------------------------------------+-------+
| checksum_offload| test_do_not_insert_checksum_on_the_transmit_packet| passed|
| checksum_offload| test_hardware_checksum_check_ip_rx | passed|
| checksum_offload| test_hardware_checksum_check_ip_tx | passed|
| checksum_offload| test_hardware_checksum_check_l4_rx | passed|
| checksum_offload| test_insert_checksum_on_the_transmit_packet | passed|
| checksum_offload| test_rx_checksum_valid_flags | passed|
| checksum_offload| test_checksum_offload_with_vlan | FAILED|
| checksum_offload| test_hardware_checksum_check_l4_tx | n/a |
| dual_vlan | test_dual_vlan_priority_rxtx | passed|
| dual_vlan | test_vlan_filter_config | passed|
| dual_vlan | test_vlan_filter_table | passed|
| dual_vlan | test_vlan_insert_config | passed|
| dual_vlan | test_vlan_random_test | passed|
| dual_vlan | test_vlan_strip_config | passed|
| dual_vlan | test_vlan_synthetic_test | passed|
| dual_vlan | test_vlan_tpid_config | passed|
| dual_vlan | test_vlan_stripq_config | n/a |
| jumboframes | test_jumboframes_bigger_jumbo | passed|
| jumboframes | test_jumboframes_jumbo_jumbo | passed|
| jumboframes | test_jumboframes_jumbo_nojumbo | passed|
| jumboframes | test_jumboframes_normal_jumbo | passed|
| jumboframes | test_jumboframes_normal_nojumbo | passed|
| rxtx_offload | test_rxoffload_port_all | passed|
| rxtx_offload | test_rxoffload_port_cmdline | passed|
| rxtx_offload | test_txoffload_port | passed|
| rxtx_offload | test_txoffload_port_all | passed|
| rxtx_offload | test_txoffload_port_checksum | passed|
| rxtx_offload | test_txoffload_port_cmdline | passed|
| rxtx_offload | test_txoffload_port_multi_segs | passed|
| rxtx_offload | test_txoffload_queue | passed|
| rxtx_offload | test_rxoffload_queue | n/a |
+-----------------+---------------------------------------------------+-------+
DPDK STV team
parent reply other threads:[~2025-11-25 7:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <553996$6i5mrh@smtpauth.intel.com>]
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=SJ0PR19MB4606FAC1A477B65FC4AF1CEBF5D1A@SJ0PR19MB4606.namprd19.prod.outlook.com \
--to=pravin.bathija@dell.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=maxime.coquelin@redhat.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).