From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw154231 [PATCH] [v18] trace: add PMU
Date: Mon, 09 Jun 2025 17:51:11 -0700 (PDT) [thread overview]
Message-ID: <6847817f.170a0220.3128b3.60e6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250609165736.2255515-1-thomas@monjalon.net>
Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/154231
_Testing issues_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Monday, June 09 2025 16:55:24
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:98bfa438ca7f80baf155636364377be72b4c75dc
154231 --> testing issues
Upstream job id: Generic-DPDK-Compile-ABI#129521
Test environment and result as below:
+-------------------------------+----------+
| Environment | abi_test |
+===============================+==========+
| CentOS Stream 9 | PASS |
+-------------------------------+----------+
| CentOS Stream 10 | FAIL |
+-------------------------------+----------+
| Debian GNU/Linux 12 | PASS |
+-------------------------------+----------+
| Fedora 40 (Clang) | FAIL |
+-------------------------------+----------+
| Fedora 40 | FAIL |
+-------------------------------+----------+
| Fedora 41 (Clang) | FAIL |
+-------------------------------+----------+
| Fedora 41 | FAIL |
+-------------------------------+----------+
| openSUSE Leap 15.6 | PASS |
+-------------------------------+----------+
| Red Hat Enterprise Linux 8.10 | PASS |
+-------------------------------+----------+
| Red Hat Enterprise Linux 9.5 | PASS |
+-------------------------------+----------+
| Ubuntu 22.04 | PASS |
+-------------------------------+----------+
| Ubuntu 24.04 | PASS |
+-------------------------------+----------+
==== 20 line log output for Fedora 41 (abi_test): ====
55 | __VA_ARGS__ \
| ^~~~~~~~~~~
../lib/eal/include/rte_eal_trace.h:133:1: note: in expansion of macro 'RTE_TRACE_POINT_FP'
133 | RTE_TRACE_POINT_FP(
| ^~~~~~~~~~~~~~~~~~
In file included from ../lib/eal/include/rte_eal_trace.h:131,
from ../lib/eal/common/eal_common_trace_points.c:7:
../lib/pmu/rte_pmu.h:236:27: note: expected 'unsigned int' but argument is of type 'char * (*)(const char *, int)'
236 | rte_pmu_read(unsigned int index)
| ~~~~~~~~~~~~~^~~~~
../lib/eal/include/rte_eal_trace.h:136:18: warning: unused variable 'val' [-Wunused-variable]
136 | uint64_t val = rte_pmu_read(index);
| ^~~
../lib/eal/include/rte_trace_point_register.h:55:9: note: in definition of macro '__RTE_TRACE_POINT'
55 | __VA_ARGS__ \
| ^~~~~~~~~~~
../lib/eal/include/rte_eal_trace.h:133:1: note: in expansion of macro 'RTE_TRACE_POINT_FP'
133 | RTE_TRACE_POINT_FP(
| ^~~~~~~~~~~~~~~~~~
ninja: build stopped: subcommand failed.
==== End log output ====
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
CentOS Stream 10
Kernel: Depends on container host
Compiler: gcc 14.2.1 20241104 (Red Hat 14.2.1-6)
Debian GNU/Linux 12
Kernel: 5.15
Compiler: gcc gcc (Debian 12.2.0-14) 12.2.0
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.8 (Fedora 18.1.8-1.fc40)
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora 41 (Clang)
Kernel: Depends on container host
Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)
Fedora 41
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
openSUSE Leap 15.6
Kernel: 5.15
Compiler: gcc gcc (SUSE Linux) 7.5.0
Red Hat Enterprise Linux 8.10
Kernel: 5.15
Compiler: gcc gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-22)
Red Hat Enterprise Linux 9.5
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 24.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33364/
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-06-10 0:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250609165736.2255515-1-thomas@monjalon.net>
2025-06-09 16:23 ` |SUCCESS| pw154231 [PATCH v18] " qemudev
2025-06-09 16:28 ` |FAILURE| " qemudev
2025-06-09 16:57 ` |SUCCESS| " checkpatch
2025-06-09 17:24 ` |FAILURE| " 0-day Robot
2025-06-09 22:04 ` |FAILURE| pw154231 [PATCH] [v18] " dpdklab
2025-06-09 22:05 ` dpdklab
2025-06-09 22:10 ` |SUCCESS| " dpdklab
2025-06-09 22:12 ` dpdklab
2025-06-09 22:18 ` |FAILURE| " dpdklab
2025-06-09 22:34 ` |PENDING| " dpdklab
2025-06-09 22:37 ` |FAILURE| " dpdklab
2025-06-09 22:40 ` dpdklab
2025-06-09 23:04 ` |SUCCESS| " dpdklab
2025-06-09 23:48 ` |FAILURE| " dpdklab
2025-06-10 0:19 ` |WARNING| " dpdklab
2025-06-10 0:20 ` |FAILURE| " dpdklab
2025-06-10 0:21 ` dpdklab
2025-06-10 0:22 ` dpdklab
2025-06-10 0:23 ` dpdklab
2025-06-10 0:51 ` dpdklab [this message]
2025-06-10 3:02 ` dpdklab
2025-06-10 3:12 ` dpdklab
2025-06-10 3:16 ` dpdklab
2025-06-10 3:26 ` dpdklab
2025-06-10 4:52 ` dpdklab
2025-06-10 4:53 ` dpdklab
2025-06-10 4:53 ` dpdklab
2025-06-10 4:53 ` 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=6847817f.170a0220.3128b3.60e6SMTPIN_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).