From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw149309 [PATCH] [v2] net/nfp: implement the burst mode ge
Date: Tue, 07 Jan 2025 01:20:34 -0800 (PST) [thread overview]
Message-ID: <677cf1e2.050a0220.2b06d0.1635SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241219014954.1763729-1-chaoyong.he@corigine.com>
Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/149309
_Testing issues_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Thursday, December 19 2024 01:49:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:78d0246a2e2fb14cba220d507192d12d2ce896ac
149309 --> testing issues
Upstream job id: Generic-DPDK-Compile-ABI#109513
Test environment and result as below:
+-------------------+----------+
| Environment | abi_test |
+===================+==========+
| Debian 12 | PEND |
+-------------------+----------+
| CentOS Stream 9 | PEND |
+-------------------+----------+
| Fedora 40 (Clang) | PEND |
+-------------------+----------+
| Fedora 40 | FAIL |
+-------------------+----------+
| Fedora 41 (Clang) | PEND |
+-------------------+----------+
| Fedora 41 | PEND |
+-------------------+----------+
| openSUSE Leap 15 | PEND |
+-------------------+----------+
| Ubuntu 24.04 | PEND |
+-------------------+----------+
| RHEL8 | PEND |
+-------------------+----------+
| Ubuntu 22.04 | PEND |
+-------------------+----------+
| RHEL9 | PEND |
+-------------------+----------+
==== 20 line log output for Fedora 40 (abi_test): ====
Error: cannot find librte_net_memif.so.24.0 in build_install
Error: cannot find librte_common_mlx5.so.24.0 in build_install
Error: cannot find librte_bus_dpaa.so.24.0 in build_install
Error: cannot find librte_crypto_caam_jr.so.24.0 in build_install
Error: cannot find librte_crypto_dpaa_sec.so.24.0 in build_install
Error: cannot find librte_net_cpfl.so.24.0 in build_install
Error: cannot find librte_baseband_turbo_sw.so.24.0 in build_install
Error: cannot find librte_common_cpt.so.24.0 in build_install
Error: cannot find librte_net_vdev_netvsc.so.24.0 in build_install
Error: cannot find librte_regex_cn9k.so.24.0 in build_install
Error: cannot find librte_net_iavf.so.24.0 in build_install
Error: cannot find librte_compress_zlib.so.24.0 in build_install
Error: cannot find librte_event_dpaa2.so.24.0 in build_install
Error: cannot find librte_baseband_la12xx.so.24.0 in build_install
Error: cannot find librte_net_pfe.so.24.0 in build_install
Error: cannot find librte_cryptodev.so.24.0 in build_install
Error: cannot find librte_bitratestats.so.24.0 in build_install
Error: cannot find librte_net_tap.so.24.0 in build_install
Error: cannot find librte_member.so.24.0 in build_install
Error: cannot find librte_gro.so.24.0 in build_install
==== End log output ====
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
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
Ubuntu 24.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.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
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/32164/
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 9:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241219014954.1763729-1-chaoyong.he@corigine.com>
2024-12-19 1:19 ` |SUCCESS| pw149309 [PATCH v2] net/nfp: implement the burst mode get operation qemudev
2024-12-19 1:23 ` qemudev
2024-12-19 1:50 ` checkpatch
2024-12-19 2:43 ` 0-day Robot
2024-12-19 3:30 ` |PENDING| pw149309 [PATCH] [v2] net/nfp: implement the burst mode ge dpdklab
2024-12-19 3:38 ` |SUCCESS| " dpdklab
2024-12-19 3:39 ` dpdklab
2024-12-19 3:44 ` dpdklab
2024-12-19 3:44 ` dpdklab
2024-12-19 3:46 ` dpdklab
2024-12-19 3:48 ` dpdklab
2024-12-19 3:51 ` dpdklab
2024-12-19 3:52 ` dpdklab
2024-12-19 3:54 ` dpdklab
2024-12-19 4:09 ` dpdklab
2024-12-19 4:09 ` dpdklab
2024-12-19 4:34 ` dpdklab
2024-12-19 4:35 ` |WARNING| " dpdklab
2024-12-19 4:35 ` |SUCCESS| " dpdklab
2024-12-19 4:41 ` dpdklab
2024-12-19 4:49 ` |WARNING| " dpdklab
2024-12-19 4:51 ` dpdklab
2024-12-19 5:30 ` |SUCCESS| " dpdklab
2024-12-19 6:47 ` dpdklab
2025-01-07 9:20 ` dpdklab [this message]
2025-01-07 10:15 ` |WARNING| " dpdklab
2025-01-08 9:21 ` |PENDING| " 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=677cf1e2.050a0220.2b06d0.1635SMTPIN_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).