From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] 49c5a4aa52658c80359b63e712c80a4dac135259
Date: Fri, 19 Dec 2025 23:39:16 -0800 (PST) [thread overview]
Message-ID: <694652a4.050a0220.12aa94.7732SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: tags/v24.11
49c5a4aa52658c80359b63e712c80a4dac135259 --> testing pass
Upstream job id: Generic-DPDK-Compile-ABI#136078
Test environment and result as below:
+------------------------------+----------+
| Environment | abi_test |
+==============================+==========+
| openSUSE Leap 15.6 | PASS |
+------------------------------+----------+
| Fedora Linux 42 | PASS |
+------------------------------+----------+
| Ubuntu 24.04 | PASS |
+------------------------------+----------+
| CentOS Stream 10 | PASS |
+------------------------------+----------+
| Debian GNU/Linux 12 | PASS |
+------------------------------+----------+
| Red Hat Enterprise Linux 9.7 | PASS |
+------------------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------------------+----------+
| CentOS Stream 9 | PASS |
+------------------------------+----------+
openSUSE Leap 15.6
Kernel: 5.15
Compiler: gcc gcc (SUSE Linux) 7.5.0
Fedora Linux 42
Kernel: 5.15
Compiler: clang gcc (GCC) 15.2.1 20251111 (Red Hat 15.2.1-4)
Ubuntu 24.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
CentOS Stream 10
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.3.1 20251022 (Red Hat 14.3.1-4)
Debian GNU/Linux 12
Kernel: 5.15
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
Red Hat Enterprise Linux 9.7
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11)
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0
CentOS Stream 9
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-14)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/35901/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-12-20 7:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-20 7:39 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-22 8:27 dpdklab
2025-12-22 7:36 dpdklab
2025-12-22 7:36 dpdklab
2025-12-22 7:12 dpdklab
2025-12-22 7:07 dpdklab
2025-12-22 6:27 dpdklab
2025-12-22 6:27 dpdklab
2025-12-22 6:07 dpdklab
2025-12-22 5:47 dpdklab
2025-12-22 5:42 dpdklab
2025-12-21 8:13 dpdklab
2025-12-21 7:55 dpdklab
2025-12-21 7:49 dpdklab
2025-12-21 7:41 dpdklab
2025-12-21 7:21 dpdklab
2025-12-21 7:20 dpdklab
2025-12-21 6:57 dpdklab
2025-12-21 6:50 dpdklab
2025-12-21 6:29 dpdklab
2025-12-21 6:29 dpdklab
2025-12-21 6:19 dpdklab
2025-12-21 5:55 dpdklab
2025-12-21 5:32 dpdklab
2025-12-21 5:30 dpdklab
2025-12-21 1:30 dpdklab
2025-12-20 9:08 dpdklab
2025-12-20 8:59 dpdklab
2025-12-20 8:57 dpdklab
2025-12-20 8:44 dpdklab
2025-12-20 8:14 dpdklab
2025-12-20 7:27 dpdklab
2025-12-20 7:19 dpdklab
2025-12-20 7:08 dpdklab
2025-12-20 6:26 dpdklab
2025-12-20 5:46 dpdklab
2025-12-20 5:44 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=694652a4.050a0220.12aa94.7732SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).