From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw159031 [PATCH] [v3] event/cnxk: fix offload flags
Date: Wed, 26 Nov 2025 08:35:30 -0800 (PST) [thread overview]
Message-ID: <69272c52.050a0220.272c61.8eb6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251126081353.85811-1-pbhagavatula@marvell.com>
Test-Label: iol-unit-arm64-testing
Test-Status: WARNING
http://dpdk.org/patch/159031
_Testing issues_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Wednesday, November 26 2025 08:13:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2815d5065694eb9d0b43c312d17a00d2356e36f1
159031 --> testing issues
Upstream job id: Generic-Unit-Test-DPDK#396091
Test environment and result as below:
+------------------------------+----------------+---------------------------+------------------------------+--------------+
| Environment | dpdk_unit_test | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | lpm_autotest |
+==============================+================+===========================+==============================+==============+
| Ubuntu 24.04 | PASS | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+---------------------------+------------------------------+--------------+
| Ubuntu 22.04 | PASS | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+---------------------------+------------------------------+--------------+
| Fedora Linux 40 | PASS | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+---------------------------+------------------------------+--------------+
| Fedora Linux 42 | PASS | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+---------------------------+------------------------------+--------------+
| Red Hat Enterprise Linux 9.5 | WARN | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+---------------------------+------------------------------+--------------+
| Ubuntu 20.04 | WARN | SKIPPED | SKIPPED | PASS |
+------------------------------+----------------+---------------------------+------------------------------+--------------+
| Debian GNU/Linux 12 | WARN | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+---------------------------+------------------------------+--------------+
| CentOS Stream 10 | WARN | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+---------------------------+------------------------------+--------------+
| CentOS Stream 9 | WARN | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+---------------------------+------------------------------+--------------+
| Fedora Linux 41 | PASS | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+---------------------------+------------------------------+--------------+
| Debian 12 (arm) | SKIPPED | WARN | WARN | SKIPPED |
+------------------------------+----------------+---------------------------+------------------------------+--------------+
==== 20 line log output for Debian 12 (arm) (cryptodev_sw_snow3g_autotest): ====
../drivers/net/cnxk/cn10k_rx.h:575:37: error: 'inb_priv' may be used uninitialized [-Werror=maybe-uninitialized]
575 | struct cn10k_inb_priv_data *inb_priv;
| ^~~~~~~~
../drivers/net/cnxk/cn10k_rx.h:575:37: error: 'inb_priv' may be used uninitialized [-Werror=maybe-uninitialized]
../drivers/net/cnxk/cn10k_rx.h:575:37: error: 'inb_priv' may be used uninitialized [-Werror=maybe-uninitialized]
../drivers/net/cnxk/cn10k_rx.h:575:37: error: 'inb_priv' may be used uninitialized [-Werror=maybe-uninitialized]
../drivers/net/cnxk/cn10k_rx.h: In function 'cn10k_sso_port_quiesce':
../drivers/net/cnxk/cn10k_rx.h:575:37: error: 'inb_priv' may be used uninitialized [-Werror=maybe-uninitialized]
../drivers/net/cnxk/cn10k_rx.h:575:37: error: 'inb_priv' may be used uninitialized [-Werror=maybe-uninitialized]
../drivers/net/cnxk/cn10k_rx.h:575:37: error: 'inb_priv' may be used uninitialized [-Werror=maybe-uninitialized]
../drivers/net/cnxk/cn10k_rx.h:575:37: error: 'inb_priv' may be used uninitialized [-Werror=maybe-uninitialized]
../drivers/net/cnxk/cn10k_rx.h:575:37: error: 'inb_priv' may be used uninitialized [-Werror=maybe-uninitialized]
../drivers/net/cnxk/cn10k_rx.h:575:37: error: 'inb_priv' may be used uninitialized [-Werror=maybe-uninitialized]
../drivers/net/cnxk/cn10k_rx.h:575:37: error: 'inb_priv' may be used uninitialized [-Werror=maybe-uninitialized]
../drivers/net/cnxk/cn10k_rx.h:575:37: error: 'inb_priv' may be used uninitialized [-Werror=maybe-uninitialized]
cc1: all warnings being treated as errors
[3199/3829] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn10k_deq_64_79_burst.c.o
[3200/3829] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn10k_deq_80_95_burst.c.o
[3201/3829] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn10k_deq_96_111_burst.c.o
ninja: build stopped: subcommand failed.
==== End log output ====
Ubuntu 24.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Ubuntu 22.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Fedora Linux 40
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora Linux 42
Kernel: 5.4
Compiler: gcc gcc (GCC) 15.2.1 20250808 (Red Hat 15.2.1-1)
Red Hat Enterprise Linux 9.5
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)
Ubuntu 20.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Debian GNU/Linux 12
Kernel: 5.4
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
CentOS Stream 10
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-8)
CentOS Stream 9
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11)
Fedora Linux 41
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
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/34681/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2025-11-26 16:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251126081353.85811-1-pbhagavatula@marvell.com>
2025-11-26 7:39 ` |SUCCESS| pw159031 [PATCH v3] " qemudev
2025-11-26 7:45 ` qemudev
2025-11-26 8:13 ` checkpatch
2025-11-26 8:52 ` |PENDING| pw159031 [PATCH] [v3] " dpdklab
2025-11-26 8:53 ` dpdklab
2025-11-26 8:54 ` |SUCCESS| " dpdklab
2025-11-26 8:59 ` dpdklab
2025-11-26 9:11 ` |PENDING| " dpdklab
2025-11-26 9:11 ` |FAILURE| " dpdklab
2025-11-26 9:14 ` |SUCCESS| " dpdklab
2025-11-26 9:16 ` dpdklab
2025-11-26 9:16 ` |FAILURE| " dpdklab
2025-11-26 9:19 ` |PENDING| " dpdklab
2025-11-26 9:24 ` |SUCCESS| " dpdklab
2025-11-26 9:25 ` dpdklab
2025-11-26 9:32 ` |PENDING| " dpdklab
2025-11-26 9:34 ` |SUCCESS| " dpdklab
2025-11-26 9:39 ` |FAILURE| " dpdklab
2025-11-26 9:48 ` |SUCCESS| " dpdklab
2025-11-26 9:57 ` dpdklab
2025-11-26 10:05 ` dpdklab
2025-11-26 10:07 ` |FAILURE| " dpdklab
2025-11-26 11:07 ` |FAILURE| pw159031 [PATCH v3] " 0-day Robot
2025-11-26 13:56 ` |FAILURE| pw159031 [PATCH] [v3] " dpdklab
2025-11-26 14:22 ` dpdklab
2025-11-26 14:23 ` dpdklab
2025-11-26 16:35 ` dpdklab [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=69272c52.050a0220.272c61.8eb6SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--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).