DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <mcoqueli@redhat.com>
To: "Bathija, Pravin" <Pravin.Bathija@dell.com>
Cc: fengchengwen <fengchengwen@huawei.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	 "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: |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, 6 Jan 2026 11:40:40 +0100	[thread overview]
Message-ID: <CAO55csy0QDUVdgs7ezRJuf9hD6gkwTvCd6zhHXj2xTwRpdgO5Q@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR19MB46060E3FBC2D4E7B0FD4BCCFF5ADA@SJ0PR19MB4606.namprd19.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 6172 bytes --]

Hi Pravin,

It seems you didn't put me in copy of the v5 revision.
Could you please resend the v5 with following the submission process as
documented in the DPDK documentation?

Best regards,
Maxime

On Mon, Dec 15, 2025 at 9:29 AM Bathija, Pravin <Pravin.Bathija@dell.com>
wrote:

> Hello again Fengcheng, Maxime,
>
> Any thoughts on when my changes will be merged into dpdk mainline ? Some
> of the SPDK test suites we plan to merge are dependent on this change.
> Please provide your input at your earliest convenience.
>
> Regards,
> Pravin
>
>
> Internal Use - Confidential
> > -----Original Message-----
> > From: Bathija, Pravin
> > Sent: Tuesday, December 9, 2025 1:06 AM
> > To: 'fengchengwen' <fengchengwen@huawei.com>; 'Maxime Coquelin'
> > <maxime.coquelin@redhat.com>; 'dev@dpdk.org' <dev@dpdk.org>
> > Subject: RE: |Smoke |FAILURE| pw(158765-158768) sid(36689)
> > job(PER_PATCH_BUILD17274-20251113210704) [v5,4/4] vhost_user: Function
> > defs for add/rem mem regions
> >
> > Dear Fencheng, Maxime,
> >
> > Gentle reminder to check-in when my changes will be merged ?
> >
> > Thanks,
> > Pravin
> >
> > > -----Original Message-----
> > > From: Bathija, Pravin
> > > Sent: Monday, November 24, 2025 11:24 PM
> > > To: fengchengwen <fengchengwen@huawei.com>; Maxime Coquelin
> > > <maxime.coquelin@redhat.com>; 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
> > >
> > > 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
> > >
> > >
> > > -----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!jCHb
> > > Wx
> > > KxAWgIg6OQEvPP3-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
>
>

[-- Attachment #2: Type: text/html, Size: 9693 bytes --]

      reply	other threads:[~2026-01-06 10:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <553996$6i5mrh@smtpauth.intel.com>
2025-11-25  7:23 ` FW: " Bathija, Pravin
2025-12-09  9:06   ` Bathija, Pravin
2025-12-15  8:28     ` Bathija, Pravin
2026-01-06 10:40       ` Maxime Coquelin [this message]

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=CAO55csy0QDUVdgs7ezRJuf9hD6gkwTvCd6zhHXj2xTwRpdgO5Q@mail.gmail.com \
    --to=mcoqueli@redhat.com \
    --cc=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).