From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] 42105ccaeef093ad8c7ce11d1bde3652861b783b
Date: Mon, 03 Nov 2025 01:39:06 -0800 (PST) [thread overview]
Message-ID: <6908783a.530a0220.bdeb7.9904SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: tags/v22.11
42105ccaeef093ad8c7ce11d1bde3652861b783b --> testing pass
Upstream job id: Generic-DPDK-Compile-Meson#440133
Test environment and result as below:
+------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+==============================+====================+
| CentOS Stream 9 | PASS |
+------------------------------+--------------------+
| Ubuntu 20.04 | PASS |
+------------------------------+--------------------+
| Fedora Linux 42 | PASS |
+------------------------------+--------------------+
| Debian GNU/Linux 12 | PASS |
+------------------------------+--------------------+
| Ubuntu 24.04 | PASS |
+------------------------------+--------------------+
| Red Hat Enterprise Linux 9.5 | PASS |
+------------------------------+--------------------+
| CentOS Stream 10 | PASS |
+------------------------------+--------------------+
| Ubuntu 22.04 | PASS |
+------------------------------+--------------------+
CentOS Stream 9
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11)
Ubuntu 20.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Fedora Linux 42
Kernel: 5.4
Compiler: clang gcc (GCC) 15.2.1 20250808 (Red Hat 15.2.1-1)
Debian GNU/Linux 12
Kernel: 5.4
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
Ubuntu 24.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Red Hat Enterprise Linux 9.5
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)
CentOS Stream 10
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-8)
Ubuntu 22.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/35431/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-11-03 9:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 9:39 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-03 16:29 dpdklab
2025-11-03 15:50 dpdklab
2025-11-03 15:50 dpdklab
2025-11-03 6:32 dpdklab
2025-11-03 6:28 dpdklab
2025-11-03 6:24 dpdklab
2025-11-03 6:12 dpdklab
2025-11-03 5:32 dpdklab
2025-11-03 5:28 dpdklab
2025-11-03 5:20 dpdklab
2025-11-02 8:03 dpdklab
2025-11-02 6:27 dpdklab
2025-11-02 6:07 dpdklab
2025-11-02 5:24 dpdklab
2025-11-02 5:19 dpdklab
2025-11-02 5:17 dpdklab
2025-11-02 4:52 dpdklab
2025-11-01 10:02 dpdklab
2025-11-01 6:05 dpdklab
2025-11-01 5:49 dpdklab
2025-11-01 5:42 dpdklab
2025-11-01 5:24 dpdklab
2025-11-01 4:53 dpdklab
2025-11-01 4:37 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=6908783a.530a0220.bdeb7.9904SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--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).