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:19:37 -0700 (PDT) [thread overview]
Message-ID: <68477a19.050a0220.b74de.37ebSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250609165736.2255515-1-thomas@monjalon.net>
Test-Label: iol-unit-arm64-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-Unit-Test-DPDK#344486
Test environment and result as below:
+------------------------------+----------------+--------------+------------------------------+---------------------------+
| Environment | dpdk_unit_test | lpm_autotest | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest |
+==============================+================+==============+==============================+===========================+
| CentOS Stream 10 (ARM) | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+------------------------------+---------------------------+
| CentOS Stream 9 (ARM) | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+------------------------------+---------------------------+
| Debian GNU/Linux 12 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+------------------------------+---------------------------+
| Fedora 40 (ARM) | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+------------------------------+---------------------------+
| Fedora 40 (ARM Clang) | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+------------------------------+---------------------------+
| Fedora 41 (ARM Clang) | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+------------------------------+---------------------------+
| Fedora 41 (ARM) | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+------------------------------+---------------------------+
| Ubuntu 20.04 | PEND | WARN | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+------------------------------+---------------------------+
| Red Hat Enterprise Linux 9.5 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+------------------------------+---------------------------+
| Ubuntu 22.04 | PASS | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+------------------------------+---------------------------+
| Ubuntu 24.04 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+--------------+------------------------------+---------------------------+
| Debian 12 (arm) | SKIPPED | SKIPPED | PEND | PEND |
+------------------------------+----------------+--------------+------------------------------+---------------------------+
==== 20 line log output for Ubuntu 20.04 (lpm_autotest): ====
/usr/bin/ld: rte_ring.c:(.text+0x988): undefined reference to `rte_mcfg_tailq_write_unlock'
/usr/bin/ld: lib/librte_ring.a.p/ring_rte_ring.c.o: in function `rte_ring_list_dump':
rte_ring.c:(.text+0xb18): undefined reference to `rte_mcfg_tailq_read_lock'
/usr/bin/ld: rte_ring.c:(.text+0xb44): undefined reference to `rte_mcfg_tailq_read_unlock'
/usr/bin/ld: lib/librte_ring.a.p/ring_rte_ring.c.o: in function `rte_ring_lookup':
rte_ring.c:(.text+0xb6c): undefined reference to `rte_mcfg_tailq_read_lock'
/usr/bin/ld: rte_ring.c:(.text+0xb94): undefined reference to `rte_mcfg_tailq_read_unlock'
/usr/bin/ld: rte_ring.c:(.text+0xb9c): undefined reference to `per_lcore__rte_errno'
/usr/bin/ld: rte_ring.c:(.text+0xba0): undefined reference to `per_lcore__rte_errno'
/usr/bin/ld: rte_ring.c:(.text+0xba4): undefined reference to `per_lcore__rte_errno'
/usr/bin/ld: rte_ring.c:(.text+0xba8): undefined reference to `per_lcore__rte_errno'
/usr/bin/ld: rte_ring.c:(.text+0xbbc): undefined reference to `rte_mcfg_tailq_read_unlock'
/usr/bin/ld: lib/librte_ring.a.p/ring_rte_ring.c.o: in function `tailqinitfn_rte_ring_tailq':
rte_ring.c:(.text.startup+0x58): undefined reference to `rte_eal_tailq_register'
/usr/bin/ld: rte_ring.c:(.text.startup+0x88): undefined reference to `__rte_panic'
collect2: error: ld returned 1 exit status
[55/272] Compiling C object lib/librte_net.a.p/net_net_crc_neon.c.o
[56/272] Compiling C object lib/librte_net.so.25.2.p/net_rte_arp.c.o
[57/272] Compiling C object lib/librte_net.so.25.2.p/net_rte_ether.c.o
ninja: build stopped: subcommand failed.
==== End log output ====
CentOS Stream 10 (ARM)
Kernel: Depends on container host
Compiler: gcc 14.2.1 20241104 (Red Hat 14.2.1-6)
CentOS Stream 9 (ARM)
Kernel: Depends on container host
Compiler: 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) 12.2.0
Fedora 40 (ARM)
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora 40 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 18.1.8 (Fedora 18.1.8-1.fc40)
Fedora 41 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)
Fedora 41 (ARM)
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
Ubuntu 20.04
Kernel: 5.4
Compiler: 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)
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
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/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:19 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 ` dpdklab [this message]
2025-06-10 0:20 ` dpdklab
2025-06-10 0:21 ` dpdklab
2025-06-10 0:22 ` dpdklab
2025-06-10 0:23 ` dpdklab
2025-06-10 0:51 ` |WARNING| " dpdklab
2025-06-10 3:02 ` |FAILURE| " 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=68477a19.050a0220.b74de.37ebSMTPIN_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).