From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 20460dcffd08a4680f881c39916ae783ee830374
Date: Sun, 29 Jun 2025 18:53:24 -0700 (PDT) [thread overview]
Message-ID: <6861ee14.050a0220.328528.7520SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
20460dcffd08a4680f881c39916ae783ee830374 --> testing pass
Upstream job id: Generic-Unit-Test-DPDK#350842
Test environment and result as below:
+-------------------------------+----------------+
| Environment | dpdk_unit_test |
+===============================+================+
| Debian GNU/Linux 12 | PASS |
+-------------------------------+----------------+
| Arch Linux 20250613.0.365270 | PASS |
+-------------------------------+----------------+
| CentOS Stream 9 | PASS |
+-------------------------------+----------------+
| CentOS Stream 10 | PASS |
+-------------------------------+----------------+
| Fedora Linux 40 | PASS |
+-------------------------------+----------------+
| Ubuntu 24.04 | PASS |
+-------------------------------+----------------+
| Ubuntu 20.04 | PASS |
+-------------------------------+----------------+
| Fedora Linux 41 | PASS |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 8.10 | PASS |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 9.5 | PASS |
+-------------------------------+----------------+
| Ubuntu 22.04 | PASS |
+-------------------------------+----------------+
| Windows Server 2022 | PASS |
+-------------------------------+----------------+
Debian GNU/Linux 12
Kernel: 5.15
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
Arch Linux 20250613.0.365270
Kernel: 5.15
Compiler: gcc gcc (GCC) 15.1.1 20250425
CentOS Stream 9
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-7)
CentOS Stream 10
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-8)
Fedora Linux 40
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
Ubuntu 24.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Ubuntu 20.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Fedora Linux 41
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
Red Hat Enterprise Linux 8.10
Kernel: 5.15
Compiler: gcc gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-22)
Red Hat Enterprise Linux 9.5
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/34072/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-06-30 1:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 1:53 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-30 4:12 dpdklab
2025-06-30 2:48 dpdklab
2025-06-30 1:48 dpdklab
2025-06-30 1:32 dpdklab
2025-06-30 1:31 dpdklab
2025-06-30 1:31 dpdklab
2025-06-30 1:31 dpdklab
2025-06-30 1:08 dpdklab
2025-06-30 0:45 dpdklab
2025-06-30 0:39 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=6861ee14.050a0220.328528.7520SMTPIN_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).