DPDK CI discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: daxuex.gao@intel.com, john.mcnamara@intel.com
Cc: ci@dpdk.org, dev@dpdk.org
Subject: Re: |Smoke |FAILURE| pw(130564-130578) sid(29292) job(PER_PATCH_BUILD8809-20230830165744) [v2, 15/15] devtools: forbid inclusion of Linux header for PCI
Date: Thu, 31 Aug 2023 11:01:24 +0200	[thread overview]
Message-ID: <0bb7928a-e429-fb16-570e-4352af89c019@redhat.com> (raw)
In-Reply-To: <c279bf$o3pl63@fmsmga004-auth.fm.intel.com>

Hello,

On 30/08/2023 23:28, sys_stv@intel.com wrote:
> Test-Label: intel-Functional
> Test-Status: FAILURE
> http://dpdk.org/patch/130578
>
> _Functional issues_
>
> Submitter: David Marchand <david.marchand@redhat.com>
> Date: 2023-08-21 11:35:34
> Branch : dpdk
> CommitID: b7b8de26f3
>
> Smoke-Testing Summary : 30 Case Done, 29 Successful, 1 Failures
>
>
> OS : Ubuntu 20.04.5 LTS
> Kernel : 5.4.0-135-generic
> GCC : 9.4.0-1ubuntu1~20.04.1
> 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                   | passed|
> 	| 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_hardware_checksum_check_l4_tx                | FAILED|

It is hard to tell what is wrong with the series with this only line.

Looking at dts test python.. I don't really understand why testpmd or 
net/i40e would be impacted, only for this test.

I would expect either everything working or a catastrophic failure (like 
a crash ;-)) for all tests.


Anyway, I will need either the details for this failure or a retest.


> 	| 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


Thanks.


-- 

David Marchand


           reply	other threads:[~2023-08-31  9:01 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <c279bf$o3pl63@fmsmga004-auth.fm.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=0bb7928a-e429-fb16-570e-4352af89c019@redhat.com \
    --to=david.marchand@redhat.com \
    --cc=ci@dpdk.org \
    --cc=daxuex.gao@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.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).