From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw149385 [PATCH] [v3] app/test-flow-perf: support testing
Date: Mon, 06 Jan 2025 18:52:21 -0800 (PST) [thread overview]
Message-ID: <677c96e5.050a0220.3a0f88.8e10SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241223091600.53160-1-sunyang.wu@jaguarmicro.com>
Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/149385
_Testing issues_
Submitter: Sunyang Wu <sunyang.wu@jaguarmicro.com>
Date: Monday, December 23 2024 09:16:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fd51012de5369679e807be1d6a81d63ef15015ce
149385 --> testing issues
Upstream job id: Generic-DPDK-Compile-ABI#109234
Test environment and result as below:
+-------------------+----------+
| Environment | abi_test |
+===================+==========+
| CentOS Stream 9 | PEND |
+-------------------+----------+
| Debian 12 | PEND |
+-------------------+----------+
| Fedora 40 (Clang) | PEND |
+-------------------+----------+
| Fedora 40 | FAIL |
+-------------------+----------+
| Fedora 41 (Clang) | PEND |
+-------------------+----------+
| Fedora 41 | PEND |
+-------------------+----------+
| openSUSE Leap 15 | PEND |
+-------------------+----------+
| RHEL8 | PEND |
+-------------------+----------+
| Ubuntu 22.04 | PEND |
+-------------------+----------+
| Ubuntu 24.04 | PEND |
+-------------------+----------+
| RHEL9 | PEND |
+-------------------+----------+
==== 20 line log output for Fedora 40 (abi_test): ====
Error: cannot find librte_net_dpaa2.so.24.0 in build_install
Error: cannot find librte_gso.so.24.0 in build_install
Error: cannot find librte_eal.so.24.0 in build_install
Error: cannot find librte_ethdev.so.24.0 in build_install
Error: cannot find librte_cfgfile.so.24.0 in build_install
Error: cannot find librte_pipeline.so.24.0 in build_install
Error: cannot find librte_kvargs.so.24.0 in build_install
Error: cannot find librte_cryptodev.so.24.0 in build_install
Error: cannot find librte_mbuf.so.24.0 in build_install
Error: cannot find librte_pdump.so.24.0 in build_install
Error: cannot find librte_bpf.so.24.0 in build_install
Error: cannot find librte_dmadev.so.24.0 in build_install
Error: cannot find librte_pcapng.so.24.0 in build_install
Error: cannot find librte_mempool.so.24.0 in build_install
Error: cannot find librte_eventdev.so.24.0 in build_install
Error: cannot find librte_security.so.24.0 in build_install
Error: cannot find librte_jobstats.so.24.0 in build_install
Error: cannot find librte_cmdline.so.24.0 in build_install
Error: cannot find librte_ring.so.24.0 in build_install
Error: cannot find librte_member.so.24.0 in build_install
==== End log output ====
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
Debian 12
Kernel: Depends on container host
Compiler: 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
Kernel: Depends on container host
Compiler: gcc (SUSE Linux) 7.5.0
RHEL8
Kernel: Depends on container host
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)
Ubuntu 22.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 24.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32193/
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-01-07 2:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241223091600.53160-1-sunyang.wu@jaguarmicro.com>
2024-12-23 8:51 ` |SUCCESS| pw149385 [PATCH v3] app/test-flow-perf: support testing the flow tables query rate qemudev
2024-12-23 8:55 ` qemudev
2024-12-23 9:16 ` |WARNING| " checkpatch
2024-12-23 10:05 ` |SUCCESS| " 0-day Robot
2024-12-23 11:58 ` |PENDING| pw149385 [PATCH] [v3] app/test-flow-perf: support testing dpdklab
2024-12-23 12:04 ` |SUCCESS| " dpdklab
2024-12-23 12:05 ` dpdklab
2024-12-23 12:10 ` dpdklab
2024-12-23 12:13 ` dpdklab
2024-12-23 12:16 ` dpdklab
2024-12-23 12:19 ` dpdklab
2024-12-23 12:45 ` dpdklab
2024-12-23 12:50 ` dpdklab
2024-12-23 12:58 ` dpdklab
2024-12-23 13:03 ` |WARNING| " dpdklab
2024-12-23 13:14 ` |SUCCESS| " dpdklab
2024-12-23 13:15 ` |WARNING| " dpdklab
2024-12-23 13:16 ` dpdklab
2024-12-23 13:38 ` |SUCCESS| " dpdklab
2024-12-23 14:57 ` dpdklab
2024-12-25 8:31 ` dpdklab
2024-12-25 8:57 ` dpdklab
2025-01-07 2:52 ` dpdklab [this message]
2025-01-07 3:44 ` |WARNING| " dpdklab
2025-01-08 15:54 ` |PENDING| " dpdklab
2025-01-08 16:58 ` |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=677c96e5.050a0220.3a0f88.8e10SMTPIN_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).