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,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: |FAILURE| pw159126-159133 [PATCH] [RFC,8/8] eal: limit maximum runti
Date: Thu, 04 Dec 2025 14:18:40 -0800 (PST)	[thread overview]
Message-ID: <693208c0.050a0220.380d10.f80eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251202172626.283094-9-stephen@networkplumber.org>

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

_Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, December 02 2025 17:24:34 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:80b3e9cad7599ce01f94cd6f8f966401a77e29c1

159126-159133 --> testing issues

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

Test environment and result as below:

+------------------------------+--------------------+
|         Environment          | dpdk_meson_compile |
+==============================+====================+
| Ubuntu 20.04                 | FAIL               |
+------------------------------+--------------------+
| Fedora Linux 42              | PEND               |
+------------------------------+--------------------+
| CentOS Stream 9              | PEND               |
+------------------------------+--------------------+
| CentOS Stream 10             | PEND               |
+------------------------------+--------------------+
| Red Hat Enterprise Linux 9.5 | PEND               |
+------------------------------+--------------------+
| Debian GNU/Linux 12          | PEND               |
+------------------------------+--------------------+
| Ubuntu 24.04                 | PEND               |
+------------------------------+--------------------+
| Ubuntu 22.04                 | PEND               |
+------------------------------+--------------------+

==== 20 line log output for Ubuntu 20.04 (dpdk_meson_compile): ====
[294/3784] Generating rte_distributor_map with a custom command
[295/3784] Compiling C object lib/librte_distributor.a.p/distributor_rte_distributor_single.c.o
[296/3784] Compiling C object lib/librte_distributor.a.p/distributor_rte_distributor_match_generic.c.o
[297/3784] Linking static target lib/librte_distributor.a
[298/3784] Generating distributor.sym_chk with a custom command (wrapped by meson to capture output)
[299/3784] Compiling C object lib/librte_dmadev.a.p/dmadev_rte_dmadev.c.o
[300/3784] Linking target lib/librte_distributor.so.26.1
[301/3784] Generating symbol file lib/librte_distributor.so.26.1.p/librte_distributor.so.26.1.symbols
[302/3784] Compiling C object lib/librte_dmadev.a.p/dmadev_rte_dmadev_trace_points.c.o
[303/3784] Linking static target lib/librte_dmadev.a
[304/3784] Generating rte_dmadev_map with a custom command
[305/3784] Generating dmadev.sym_chk with a custom command (wrapped by meson to capture output)
[306/3784] Compiling C object lib/librte_efd.a.p/efd_rte_efd.c.o
FAILED: lib/librte_efd.a.p/efd_rte_efd.c.o
ccache clang -Ilib/librte_efd.a.p -Ilib -I../lib -Ilib/efd -I../lib/efd -Ilib/eal/common -I../lib/eal/common -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 -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/argparse -I../lib/argparse -Ilib/ring -I../lib/ring -Ilib/hash -I../lib/hash -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/rcu -I../lib/rcu -Xclang -fcolor-diagnostics -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O3 -include rte_config.h -Wvla -Wcast-qual -Wcomma -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-
 missing-field-initializers -D_GNU_SOURCE -target aarch64-linux-gnu --sysroot /usr/aarch64-linux-gnu -fPIC -march=armv8-a+crc -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -DRTE_LOG_DEFAULT_LOGTYPE=lib.efd -DRTE_ANNOTATE_LOCKS -Wthread-safety -MD -MQ lib/librte_efd.a.p/efd_rte_efd.c.o -MF lib/librte_efd.a.p/efd_rte_efd.c.o.d -o lib/librte_efd.a.p/efd_rte_efd.c.o -c ../lib/efd/rte_efd.c
../lib/efd/rte_efd.c:714:9: error: comparison of integers of different signs: 'int' and 'unsigned long' [-Werror,-Wsign-compare]
if (cc >= sizeof(ring_name)) {
~~ ^  ~~~~~~~~~~~~~~~~~
1 error generated.
ninja: build stopped: subcommand failed.
==== End log output ====

Ubuntu 20.04
	Kernel: 5.15
	Compiler: aarch64-linux-gnu-gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Fedora Linux 42
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 15.2.1 20250808 (Red Hat 15.2.1-1)

CentOS Stream 9
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11)

CentOS Stream 10
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-8)

Red Hat Enterprise Linux 9.5
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)

Debian GNU/Linux 12
	Kernel: 5.4
	Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-12-04 22:18 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251202172626.283094-9-stephen@networkplumber.org>
2025-12-02 17:01 ` |SUCCESS| pw159126-159133 [RFC 8/8] eal: limit maximum runtime directory and socket paths qemudev
2025-12-02 17:06 ` |FAILURE| " qemudev
2025-12-02 17:26 ` |SUCCESS| pw159133 " checkpatch
2025-12-02 22:13 ` |FAILURE| pw159126-159133 [PATCH] [RFC,8/8] eal: limit maximum runti dpdklab
2025-12-02 22:14 ` dpdklab
2025-12-02 22:15 ` |WARNING| " dpdklab
2025-12-02 22:18 ` |FAILURE| " dpdklab
2025-12-02 22:18 ` dpdklab
2025-12-02 22:18 ` dpdklab
2025-12-02 22:18 ` dpdklab
2025-12-02 22:20 ` dpdklab
2025-12-02 22:22 ` |PENDING| " dpdklab
2025-12-02 22:28 ` |FAILURE| pw159133 [RFC 8/8] eal: limit maximum runtime directory and socket paths 0-day Robot
2025-12-02 22:32 ` |FAILURE| pw159126-159133 [PATCH] [RFC,8/8] eal: limit maximum runti dpdklab
2025-12-02 22:32 ` dpdklab
2025-12-02 23:01 ` dpdklab
2025-12-02 23:02 ` dpdklab
2025-12-02 23:02 ` dpdklab
2025-12-03  1:17 ` dpdklab
2025-12-03  2:20 ` dpdklab
2025-12-03  3:08 ` dpdklab
2025-12-03  5:03 ` dpdklab
2025-12-03  6:20 ` |WARNING| " dpdklab
2025-12-04 22:18 ` dpdklab [this message]
2025-12-04 22:19 ` |FAILURE| " dpdklab
2025-12-04 22:20 ` dpdklab
2025-12-04 22:20 ` dpdklab
2025-12-04 22:20 ` dpdklab
2025-12-04 22:20 ` |SUCCESS| " dpdklab
2025-12-04 22:21 ` |FAILURE| " dpdklab
2025-12-04 22:22 ` dpdklab
2025-12-04 22:27 ` |SUCCESS| " dpdklab
2025-12-04 22:29 ` |PENDING| " dpdklab
2025-12-04 22:36 ` |WARNING| " dpdklab
2025-12-04 22:36 ` |SUCCESS| " dpdklab
2025-12-04 22:44 ` |FAILURE| " dpdklab
2025-12-04 22:47 ` |PENDING| " dpdklab
2025-12-04 22:53 ` |FAILURE| " dpdklab
2025-12-04 23:05 ` dpdklab
2025-12-04 23:17 ` |WARNING| " dpdklab
2025-12-04 23:17 ` |FAILURE| " dpdklab
2025-12-04 23:18 ` dpdklab
2025-12-04 23:25 ` dpdklab
2025-12-04 23:28 ` |WARNING| " dpdklab
2025-12-04 23:37 ` |FAILURE| " dpdklab
2025-12-04 23:46 ` dpdklab
2025-12-04 23:48 ` dpdklab
2025-12-04 23:51 ` |SUCCESS| " dpdklab
2025-12-05  0:05 ` |FAILURE| " dpdklab
2025-12-05  0:15 ` |WARNING| " dpdklab
2025-12-05  1:19 ` |FAILURE| " dpdklab
2025-12-05  2:27 ` dpdklab
2025-12-05  4:34 ` dpdklab
2025-12-05  4:37 ` dpdklab
2025-12-05 21:26 ` |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=693208c0.050a0220.380d10.f80eSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=stephen@networkplumber.org \
    --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).