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| pw158825-158828 [PATCH] [4/4] test: use unit test runner f
Date: Sat, 15 Nov 2025 12:46:44 -0800 (PST) [thread overview]
Message-ID: <6918e6b4.050a0220.3d5c8.5c1fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251115193409.99740-5-stephen@networkplumber.org>
Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/158828
_Testing issues_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Saturday, November 15 2025 19:33:10
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:be0112878b4fc3a1b918370ed2fe615c52039d77
158825-158828 --> testing issues
Upstream job id: Generic-DPDK-Compile-Meson#444879
Test environment and result as below:
+------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+==============================+====================+
| Ubuntu 20.04 | FAIL |
+------------------------------+--------------------+
| Red Hat Enterprise Linux 9.5 | FAIL |
+------------------------------+--------------------+
| Debian GNU/Linux 12 | PEND |
+------------------------------+--------------------+
| Fedora Linux 42 | FAIL |
+------------------------------+--------------------+
| Ubuntu 22.04 | FAIL |
+------------------------------+--------------------+
| Ubuntu 24.04 | FAIL |
+------------------------------+--------------------+
| CentOS Stream 9 | FAIL |
+------------------------------+--------------------+
| CentOS Stream 10 | FAIL |
+------------------------------+--------------------+
==== 20 line log output for CentOS Stream 10 (dpdk_meson_compile): ====
In function 'rte_strlcpy',
inlined from 'setup_acl_pipeline.isra' at ../app/test/test_table_acl.c:510:4:
../lib/eal/include/rte_string_fns.h:63:24: error: '%s' directive output may be truncated writing up to 639 bytes into a region of size 128 [-Werror=format-truncation=]
63 | return (size_t)snprintf(dst, size, "%s", src);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/eal/include/rte_string_fns.h:63:24: note: 'snprintf' output between 1 and 640 bytes into a destination of size 128
In function 'rte_strlcpy',
inlined from 'setup_acl_pipeline.isra' at ../app/test/test_table_acl.c:545:4:
../lib/eal/include/rte_string_fns.h:63:24: error: '%s' directive output may be truncated writing up to 639 bytes into a region of size 128 [-Werror=format-truncation=]
63 | return (size_t)snprintf(dst, size, "%s", src);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/eal/include/rte_string_fns.h:63:24: note: 'snprintf' output between 1 and 640 bytes into a destination of size 128
In function 'rte_strlcpy',
inlined from 'setup_acl_pipeline.isra' at ../app/test/test_table_acl.c:597:4:
../lib/eal/include/rte_string_fns.h:63:24: error: '%s' directive output may be truncated writing up to 639 bytes into a region of size 128 [-Werror=format-truncation=]
63 | return (size_t)snprintf(dst, size, "%s", src);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/eal/include/rte_string_fns.h:63:24: note: 'snprintf' output between 1 and 640 bytes into a destination of size 128
cc1: all warnings being treated as errors
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
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
Fedora Linux 42
Kernel: 5.4
Compiler: clang gcc (GCC) 15.2.1 20250808 (Red Hat 15.2.1-1)
Ubuntu 22.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 24.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
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)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34605/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-11-15 20:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251115193409.99740-5-stephen@networkplumber.org>
2025-11-15 19:13 ` |SUCCESS| pw158825-158828 [PATCH 4/4] test: use unit test runner for eal flags qemudev
2025-11-15 19:18 ` qemudev
2025-11-15 19:33 ` |SUCCESS| pw158828 " checkpatch
2025-11-15 20:03 ` |FAILURE| pw158825-158828 [PATCH] [4/4] test: use unit test runner f dpdklab
2025-11-15 20:05 ` |SUCCESS| " dpdklab
2025-11-15 20:07 ` |PENDING| " dpdklab
2025-11-15 20:09 ` |SUCCESS| " dpdklab
2025-11-15 20:11 ` |FAILURE| " dpdklab
2025-11-15 20:12 ` dpdklab
2025-11-15 20:12 ` dpdklab
2025-11-15 20:12 ` |WARNING| " dpdklab
2025-11-15 20:13 ` dpdklab
2025-11-15 20:21 ` |SUCCESS| " dpdklab
2025-11-15 20:21 ` |FAILURE| " dpdklab
2025-11-15 20:22 ` dpdklab
2025-11-15 20:22 ` dpdklab
2025-11-15 20:23 ` dpdklab
2025-11-15 20:24 ` |PENDING| " dpdklab
2025-11-15 20:24 ` |SUCCESS| " dpdklab
2025-11-15 20:26 ` dpdklab
2025-11-15 20:26 ` dpdklab
2025-11-15 20:42 ` |FAILURE| " dpdklab
2025-11-15 20:44 ` |WARNING| " dpdklab
2025-11-15 20:45 ` |FAILURE| " dpdklab
2025-11-15 20:46 ` dpdklab
2025-11-15 20:46 ` dpdklab [this message]
2025-11-15 20:47 ` dpdklab
2025-11-15 20:47 ` dpdklab
2025-11-15 20:47 ` dpdklab
2025-11-15 20:48 ` |FAILURE| pw158828 [PATCH 4/4] test: use unit test runner for eal flags 0-day Robot
2025-11-15 20:55 ` |SUCCESS| pw158825-158828 [PATCH] [4/4] test: use unit test runner f dpdklab
2025-11-15 21:06 ` dpdklab
2025-11-15 21:06 ` |WARNING| " dpdklab
2025-11-15 21:10 ` |FAILURE| " dpdklab
2025-11-15 21:25 ` dpdklab
2025-11-15 23:24 ` 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=6918e6b4.050a0220.3d5c8.5c1fSMTPIN_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).