From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] 63864b90e2bf91b38d9f4accb588c52ed90cac4e
Date: Sun, 11 Jan 2026 21:12:38 -0800 (PST) [thread overview]
Message-ID: <696482c6.050a0220.2ebcf1.c473SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: tags/v23.11
63864b90e2bf91b38d9f4accb588c52ed90cac4e --> testing pending
Upstream job id: Windows-Compile-DPDK-Native#33325
Test environment and result as below:
+---------------------+-------------------------+--------------------+
| Environment | dpdk_llvm_clang_compile | dpdk_meson_compile |
+=====================+=========================+====================+
| Windows Server 2025 | PASS | SKIPPED |
+---------------------+-------------------------+--------------------+
| FreeBSD 14.2 | SKIPPED | PEND |
+---------------------+-------------------------+--------------------+
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:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 5:12 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-12 6:09 dpdklab
2026-01-12 6:02 dpdklab
2026-01-12 5:47 dpdklab
2026-01-11 6:14 dpdklab
2026-01-11 5:19 dpdklab
2026-01-11 5:18 dpdklab
2026-01-11 5:17 dpdklab
2026-01-11 5:02 dpdklab
2026-01-10 17:59 dpdklab
2026-01-10 6:17 dpdklab
2026-01-08 21:12 dpdklab
2026-01-08 21:11 dpdklab
2026-01-07 6:41 dpdklab
2026-01-07 6:28 dpdklab
2026-01-07 5:26 dpdklab
2026-01-07 5:21 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=696482c6.050a0220.2ebcf1.c473SMTPIN_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).