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,
	"mannywang(Wang Yong Feng )" <mannywang@tencent.com>
Subject: |FAILURE| pw159009 [PATCH] acl: support custom memory allocator
Date: Tue, 25 Nov 2025 06:49:55 -0800 (PST)	[thread overview]
Message-ID: <6925c213.050a0220.313554.dea9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <A4D81139F2372B04+20251125094044.39320-1-mannywang@tencent.com>

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

_Testing issues_

Submitter: mannywang(Wang Yong Feng ) <mannywang@tencent.com>
Date: Tuesday, November 25 2025 09:40:43 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2815d5065694eb9d0b43c312d17a00d2356e36f1

159009 --> testing issues

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

Test environment and result as below:

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

==== 20 line log output for Ubuntu 20.04 (dpdk_meson_compile): ====
from ../lib/mbuf/rte_mbuf.h:39,
from ../app/test/test_acl.c:11:
/usr/arm-linux-gnueabihf/include/inttypes.h:57:34: note: format string is defined here
57 | # define PRId64  __PRI64_PREFIX "d"
../app/test/test_acl.c: In function 'temp_alloc':
../app/test/test_acl.c:1768:10: error: format '%lld' expects argument of type 'long long int', but argument 3 has type 'size_t' {aka 'unsigned int'} [-Werror=format=]
1768 |   printf("Line %i: alloc temp memory fail, size=%" PRId64 ", used=%d\n",
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1769 |    __LINE__,
1770 |    size,
|    ~~~~
|    |
|    size_t {aka unsigned int}
In file included from ../lib/mempool/rte_mempool.h:40,
from ../lib/mbuf/rte_mbuf.h:39,
from ../app/test/test_acl.c:11:
/usr/arm-linux-gnueabihf/include/inttypes.h:57:34: note: format string is defined here
57 | # define PRId64  __PRI64_PREFIX "d"
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====

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.15
	Compiler: aarch64-linux-gnu-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

Fedora Linux 42
	Kernel: 5.4
	Compiler: gcc 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/34668/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-11-25 14:49 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A4D81139F2372B04+20251125094044.39320-1-mannywang@tencent.com>
2025-11-25  9:07 ` |SUCCESS| " qemudev
2025-11-25  9:12 ` qemudev
2025-11-25  9:42 ` |WARNING| " checkpatch
2025-11-25 11:19 ` |FAILURE| " 0-day Robot
2025-11-25 11:23 ` |PENDING| " dpdklab
2025-11-25 11:26 ` |SUCCESS| " dpdklab
2025-11-25 11:31 ` dpdklab
2025-11-25 11:35 ` dpdklab
2025-11-25 11:50 ` |FAILURE| " dpdklab
2025-11-25 11:51 ` dpdklab
2025-11-25 11:51 ` |SUCCESS| " dpdklab
2025-11-25 11:57 ` dpdklab
2025-11-25 11:57 ` dpdklab
2025-11-25 12:01 ` |PENDING| " dpdklab
2025-11-25 12:04 ` dpdklab
2025-11-25 12:17 ` |SUCCESS| " dpdklab
2025-11-25 12:24 ` dpdklab
2025-11-25 12:28 ` |FAILURE| " dpdklab
2025-11-25 12:35 ` |SUCCESS| " dpdklab
2025-11-25 12:35 ` dpdklab
2025-11-25 12:37 ` dpdklab
2025-11-25 14:49 ` dpdklab [this message]
2025-11-25 15:37 ` dpdklab
2025-11-25 17:26 ` |FAILURE| " dpdklab
2025-11-25 18:10 ` dpdklab
2025-11-25 18:24 ` dpdklab
2025-11-25 20:12 ` |SUCCESS| " dpdklab
2025-11-25 21:19 ` dpdklab
2025-11-25 21:35 ` 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=6925c213.050a0220.313554.dea9SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=mannywang@tencent.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).