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] 63864b90e2bf91b38d9f4accb588c52ed90cac4e
Date: Sun, 11 Jan 2026 21:25:35 -0800 (PST) [thread overview]
Message-ID: <696485cf.050a0220.a902e.4abdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: tags/v23.11
63864b90e2bf91b38d9f4accb588c52ed90cac4e --> testing pass
Upstream job id: Generic-VM-DPDK-Compile-Meson#40613
Test environment and result as below:
+---------------------+-------------------------+--------------------+----------------------+
| Environment | dpdk_llvm_clang_compile | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+=========================+====================+======================+
| Windows Server 2025 | PASS | SKIPPED | PASS |
+---------------------+-------------------------+--------------------+----------------------+
| FreeBSD 14.2 | SKIPPED | PASS | SKIPPED |
+---------------------+-------------------------+--------------------+----------------------+
Windows Server 2025
Kernel: 10.0.26100
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
FreeBSD 14.2
Kernel: 14.2-RELEASE
Compiler: clang 18.1.6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/36056/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2026-01-12 5:25 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 5:25 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-12 9:51 dpdklab
2026-01-12 9:02 dpdklab
2026-01-12 7:21 dpdklab
2026-01-12 7:11 dpdklab
2026-01-12 7:11 dpdklab
2026-01-12 7:11 dpdklab
2026-01-12 7:11 dpdklab
2026-01-12 7:11 dpdklab
2026-01-12 6:28 dpdklab
2026-01-12 6:27 dpdklab
2026-01-12 5:58 dpdklab
2026-01-12 5:46 dpdklab
2026-01-12 5:30 dpdklab
2026-01-12 5:29 dpdklab
2026-01-12 5:18 dpdklab
2026-01-12 5:17 dpdklab
2026-01-11 19:38 dpdklab
2026-01-11 16:36 dpdklab
2026-01-11 16:13 dpdklab
2026-01-11 15:22 dpdklab
2026-01-11 11:49 dpdklab
2026-01-11 11:05 dpdklab
2026-01-11 10:29 dpdklab
2026-01-11 10:01 dpdklab
2026-01-11 8:41 dpdklab
2026-01-11 6:59 dpdklab
2026-01-11 6:44 dpdklab
2026-01-11 6:36 dpdklab
2026-01-11 6:02 dpdklab
2026-01-11 6:02 dpdklab
2026-01-11 5:47 dpdklab
2026-01-11 5:37 dpdklab
2026-01-11 5:35 dpdklab
2026-01-11 5:24 dpdklab
2026-01-11 5:03 dpdklab
2026-01-11 5:03 dpdklab
2026-01-11 5:02 dpdklab
2026-01-11 5:00 dpdklab
2026-01-11 4:59 dpdklab
2026-01-11 4:58 dpdklab
2026-01-11 4:58 dpdklab
2026-01-11 4:55 dpdklab
2026-01-11 4:54 dpdklab
2026-01-11 4:52 dpdklab
2026-01-11 1:57 dpdklab
2026-01-11 1:36 dpdklab
2026-01-10 23:07 dpdklab
2026-01-10 20:25 dpdklab
2026-01-10 17:04 dpdklab
2026-01-10 10:35 dpdklab
2026-01-10 9:58 dpdklab
2026-01-10 9:06 dpdklab
2026-01-10 7:53 dpdklab
2026-01-10 7:46 dpdklab
2026-01-10 6:24 dpdklab
2026-01-10 6:23 dpdklab
2026-01-10 5:52 dpdklab
2026-01-10 5:51 dpdklab
2026-01-10 5:50 dpdklab
2026-01-10 5:49 dpdklab
2026-01-10 0:41 dpdklab
2026-01-10 0:27 dpdklab
2026-01-09 21:12 dpdklab
2026-01-09 9:01 dpdklab
2026-01-09 9:01 dpdklab
2026-01-09 8:06 dpdklab
2026-01-09 8:01 dpdklab
2026-01-09 7:58 dpdklab
2026-01-09 7:54 dpdklab
2026-01-09 7:24 dpdklab
2026-01-09 6:54 dpdklab
2026-01-09 0:58 dpdklab
2026-01-09 0:14 dpdklab
2026-01-08 17:50 dpdklab
2026-01-08 15:12 dpdklab
2026-01-08 7:08 dpdklab
2026-01-08 7:06 dpdklab
2026-01-08 6:46 dpdklab
2026-01-08 6:41 dpdklab
2026-01-08 6:33 dpdklab
2026-01-08 6:13 dpdklab
2026-01-08 6:01 dpdklab
2026-01-07 13:54 dpdklab
2026-01-07 8:22 dpdklab
2026-01-07 7:40 dpdklab
2026-01-07 7:31 dpdklab
2026-01-07 7:27 dpdklab
2026-01-07 7:19 dpdklab
2026-01-07 6:39 dpdklab
2026-01-07 6:38 dpdklab
2026-01-07 5:56 dpdklab
2026-01-07 5:56 dpdklab
2026-01-07 5:50 dpdklab
2026-01-07 5:28 dpdklab
2026-01-07 5:17 dpdklab
2026-01-07 5:16 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=696485cf.050a0220.a902e.4abdSMTPIN_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).