automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Wenbo Cao <caowenbo@mucse.com>
Subject: |FAILURE| pw151613-151639 [PATCH] [v13,28/28] net/rnp: support Rx/Tx
Date: Wed, 19 Feb 2025 03:39:55 -0800 (PST)	[thread overview]
Message-ID: <67b5c30b.0c0a0220.1c1af6.be58SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1739951849-67601-29-git-send-email-caowenbo@mucse.com>

Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/151639

_Testing issues_

Submitter: Wenbo Cao <caowenbo@mucse.com>
Date: Wednesday, February 19 2025 07:57:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:968f7b6d7b6a7e60e6e551db430c4eecaccbbfd2

151613-151639 --> testing issues

Upstream job id: Generic-DPDK-Compile-Meson#362983

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| RHEL9 (ARM)                            | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile     | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK                   | FAIL               |
+----------------------------------------+--------------------+
| Fedora 40 (ARM Clang)                  | PASS               |
+----------------------------------------+--------------------+
| Fedora 41 (ARM Clang)                  | PASS               |
+----------------------------------------+--------------------+
| Fedora 41 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Fedora 40 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 22.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 24.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM)                  | PASS               |
+----------------------------------------+--------------------+
| CentOS Stream 10 (ARM)                 | PASS               |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM)               | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+
| Debian 12 (arm)                        | PASS               |
+----------------------------------------+--------------------+

==== 20 line log output for Debian 12 with MUSDK (dpdk_meson_compile): ====
[888/1284] Linking static target drivers/libtmp_rte_net_r8169.a
[889/1284] Generating rte_net_r8169.pmd.c with a custom command
[890/1284] Compiling C object drivers/librte_net_r8169.a.p/meson-generated_.._rte_net_r8169.pmd.c.o
[891/1284] Linking static target drivers/librte_net_r8169.a
[892/1284] Compiling C object drivers/librte_net_r8169.so.25.1.p/meson-generated_.._rte_net_r8169.pmd.c.o
[893/1284] Linking target drivers/librte_net_r8169.so.25.1
[894/1284] Compiling C object drivers/net/rnp/base/librnp_base.a.p/rnp_mbx.c.o
[895/1284] Compiling C object drivers/net/rnp/base/librnp_base.a.p/rnp_fw_cmd.c.o
[896/1284] Compiling C object drivers/net/rnp/base/librnp_base.a.p/rnp_mbx_fw.c.o
FAILED: drivers/net/rnp/base/librnp_base.a.p/rnp_mbx_fw.c.o
ccache aarch64-linux-gnu-gcc -Idrivers/net/rnp/base/librnp_base.a.p -Idrivers/net/rnp/base -I../drivers/net/rnp/base -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/arm/include -I../lib/eal/arm/include -I../kernel/linux -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/ethdev -I../lib/ethdev -Ilib/meter -I../lib/meter -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O3 -include rte_config.h -Wvla -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-st
 rings -Wno-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -mcpu=cortex-a72 -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -Wno-address-of-packed-member -DRTE_LIBRTE_IXGBE_BYPASS -Wno-unused-value -Wno-unused-but-set-variable -Wno-unused-parameter -MD -MQ drivers/net/rnp/base/librnp_base.a.p/rnp_mbx_fw.c.o -MF drivers/net/rnp/base/librnp_base.a.p/rnp_mbx_fw.c.o.d -o drivers/net/rnp/base/librnp_base.a.p/rnp_mbx_fw.c.o -c ../drivers/net/rnp/base/rnp_mbx_fw.c
../drivers/net/rnp/base/rnp_mbx_fw.c: In function 'rnp_mbx_fw_get_capability':
../drivers/net/rnp/base/rnp_mbx_fw.c:257:65: error: 'ability' may be used uninitialized [-Werror=maybe-uninitialized]
257 |                         hw->phy_port_ids[idx] = ability.port_ids[idx];
|                                                 ~~~~~~~~~~~~~~~~^~~~~
../drivers/net/rnp/base/rnp_mbx_fw.c:235:38: note: 'ability' declared here
235 |         struct rnp_phy_abilities_rep ability;
|                                      ^~~~~~~
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====

RHEL9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: Depends on container host
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Ubuntu 20.04 ARM SVE
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

Debian 12 with MUSDK
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

Fedora 40 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.8 (Fedora 18.1.8-1.fc40)

Fedora 41 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)

Fedora 41 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)

Fedora 40 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)

Ubuntu 20.04 (ARM)
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Ubuntu 22.04 (ARM)
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 24.04 (ARM)
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

CentOS Stream 9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

CentOS Stream 10 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20241104 (Red Hat 14.2.1-6)

Debian 11 (Buster) (ARM)
	Kernel: Depends on container host
	Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110

Ubuntu 20.04 ARM Clang Cross Compile
	Kernel: Depends on container host
	Compiler: clang 10.0.0-4ubuntu1

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: Depends on container host
	Compiler: gcc 9.4.0

Debian 12 (arm)
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32609/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2025-02-19 11:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1739951849-67601-29-git-send-email-caowenbo@mucse.com>
2025-02-19  7:28 ` |SUCCESS| pw151613-151639 [PATCH v13 28/28] net/rnp: support Rx/Tx burst mode info qemudev
2025-02-19  7:32 ` qemudev
2025-02-19  8:05 ` |SUCCESS| pw151639 " checkpatch
2025-02-19  9:04 ` 0-day Robot
2025-02-19  9:09 ` |SUCCESS| pw151613-151639 [PATCH] [v13,28/28] net/rnp: support Rx/Tx dpdklab
2025-02-19  9:13 ` dpdklab
2025-02-19  9:15 ` dpdklab
2025-02-19  9:37 ` |PENDING| " dpdklab
2025-02-19  9:39 ` dpdklab
2025-02-19  9:45 ` dpdklab
2025-02-19  9:49 ` |SUCCESS| " dpdklab
2025-02-19 10:12 ` dpdklab
2025-02-19 10:13 ` |PENDING| " dpdklab
2025-02-19 10:17 ` |FAILURE| " dpdklab
2025-02-19 10:23 ` dpdklab
2025-02-19 10:29 ` |SUCCESS| " dpdklab
2025-02-19 10:32 ` dpdklab
2025-02-19 10:32 ` dpdklab
2025-02-19 10:40 ` dpdklab
2025-02-19 10:49 ` dpdklab
2025-02-19 11:38 ` |FAILURE| " dpdklab
2025-02-19 11:39 ` dpdklab [this message]
2025-02-19 15:10 ` |SUCCESS| " 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=67b5c30b.0c0a0220.1c1af6.be58SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=caowenbo@mucse.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).