automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: rbhansali@marvell.com, robot@bytheb.org
Subject: |FAILURE| pw152520 [PATCH 3/3] net/cnxk: update IP header of reassembled packets
Date: Fri, 21 Mar 2025 08:03:44 -0400	[thread overview]
Message-ID: <20250321120344.1995917-1-robot@bytheb.org> (raw)
In-Reply-To: <20250321100343.1081664-3-rbhansali@marvell.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/152520/

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/13989700742
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-ppc64le" failed at step Build and test
"ubuntu-22.04-gcc-riscv64" failed at step Build and test
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-ppc64le" at step Build and test
####################################################################################
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-ppc64le" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-riscv64" at step Build and test
####################################################################################
  429 |                                 fsz_w1 = finfo->w1.u64;
      |                                 ~~~~~~~^~~~~~~~~~~~~~~
../drivers/net/cnxk/cn20k_rx.h:311:39: note: ‘finfo’ was declared here
  311 |         const struct cpt_frag_info_s *finfo;
      |                                       ^~~~~
../drivers/net/cnxk/cn20k_rx.h:429:40: error: ‘finfo’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
  429 |                                 fsz_w1 = finfo->w1.u64;
      |                                 ~~~~~~~^~~~~~~~~~~~~~~
../drivers/net/cnxk/cn20k_rx.h:311:39: note: ‘finfo’ was declared here
  311 |         const struct cpt_frag_info_s *finfo;
      |                                       ^~~~~
../drivers/net/cnxk/cn20k_rx.h:429:40: error: ‘finfo’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
  429 |                                 fsz_w1 = finfo->w1.u64;
      |                                 ~~~~~~~^~~~~~~~~~~~~~~
../drivers/net/cnxk/cn20k_rx.h:311:39: note: ‘finfo’ was declared here
  311 |         const struct cpt_frag_info_s *finfo;
      |                                       ^~~~~
cc1: all warnings being treated as errors
[856/5905] Compiling C object drivers/libtmp_rte_power_kvm_vm.a.p/power_kvm_vm_kvm_vm.c.o
[857/5905] Compiling C object drivers/libtmp_rte_baseband_fpga_5gnr_fec.a.p/baseband_fpga_5gnr_fec_rte_fpga_5gnr_fec.c.o
[858/5905] Compiling C object drivers/libtmp_rte_baseband_fpga_lte_fec.a.p/baseband_fpga_lte_fec_fpga_lte_fec.c.o
[859/5905] Compiling C object drivers/libtmp_rte_baseband_acc.a.p/baseband_acc_rte_acc100_pmd.c.o
[860/5905] Compiling C object drivers/libtmp_rte_baseband_acc.a.p/baseband_acc_rte_vrb_pmd.c.o
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-riscv64" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2025-03-21 12:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250321100343.1081664-3-rbhansali@marvell.com>
2025-03-21  9:31 ` |SUCCESS| pw152518-152520 " qemudev
2025-03-21  9:35 ` qemudev
2025-03-21 10:05 ` |SUCCESS| pw152520 " checkpatch
2025-03-21 11:53 ` |SUCCESS| pw152518-152520 [PATCH] [3/3] net/cnxk: update IP header o dpdklab
2025-03-21 11:58 ` dpdklab
2025-03-21 12:03 ` 0-day Robot [this message]
2025-03-21 12:06 ` dpdklab
2025-03-21 12:07 ` |PENDING| " dpdklab
2025-03-21 12:08 ` |SUCCESS| " dpdklab
2025-03-21 12:12 ` dpdklab
2025-03-21 12:13 ` dpdklab
2025-03-21 12:14 ` dpdklab
2025-03-21 12:24 ` dpdklab
2025-03-21 12:34 ` dpdklab
2025-03-21 12:59 ` dpdklab
2025-03-21 13:06 ` dpdklab
2025-03-21 13:07 ` dpdklab
2025-03-21 13:37 ` dpdklab
2025-03-21 13:37 ` dpdklab
2025-03-21 13:47 ` |FAILURE| " dpdklab
2025-03-21 13:59 ` |PENDING| " dpdklab
2025-03-21 14:43 ` |SUCCESS| " dpdklab
2025-03-21 15:37 ` dpdklab
2025-03-21 16:14 ` dpdklab
2025-03-21 16:16 ` dpdklab
2025-03-21 16:17 ` dpdklab
2025-03-21 16:47 ` dpdklab
2025-03-21 21:34 ` dpdklab

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=20250321120344.1995917-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=rbhansali@marvell.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).