From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] 49c5a4aa52658c80359b63e712c80a4dac135259
Date: Sun, 11 Jan 2026 21:22:27 -0800 (PST) [thread overview]
Message-ID: <69648513.050a0220.1932aa.1603SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: tags/v24.11
49c5a4aa52658c80359b63e712c80a4dac135259 --> testing pending
Upstream job id: Windows-Compile-DPDK-Native#33327
Test environment and result as below:
+---------------------+--------------------+-------------------------+
| Environment | dpdk_meson_compile | dpdk_llvm_clang_compile |
+=====================+====================+=========================+
| FreeBSD 14.2 | PEND | SKIPPED |
+---------------------+--------------------+-------------------------+
| Windows Server 2025 | SKIPPED | PASS |
+---------------------+--------------------+-------------------------+
FreeBSD 14.2
Kernel: 14.2-RELEASE
Compiler: clang 18.1.6
Windows Server 2025
Kernel: 10.0.26100
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/36057/
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:22 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 5:22 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-12 7:03 dpdklab
2026-01-12 5:47 dpdklab
2026-01-12 0:40 dpdklab
2026-01-11 6:14 dpdklab
2026-01-11 5:53 dpdklab
2026-01-11 5:41 dpdklab
2026-01-11 5:24 dpdklab
2026-01-11 5:06 dpdklab
2026-01-10 18:08 dpdklab
2026-01-10 6:18 dpdklab
2026-01-09 13:33 dpdklab
2026-01-08 21:58 dpdklab
2026-01-08 21:24 dpdklab
2026-01-07 5:30 dpdklab
2026-01-07 5:13 dpdklab
2026-01-07 5:12 dpdklab
2026-01-07 5:10 dpdklab
2026-01-06 5:10 dpdklab
2026-01-06 5:09 dpdklab
2026-01-05 6:06 dpdklab
2026-01-05 5:10 dpdklab
2026-01-04 6:46 dpdklab
2026-01-04 5:34 dpdklab
2026-01-04 5:10 dpdklab
2026-01-03 7:26 dpdklab
2026-01-03 7:09 dpdklab
2026-01-03 6:15 dpdklab
2026-01-03 5:10 dpdklab
2026-01-02 5:46 dpdklab
2026-01-02 5:39 dpdklab
2026-01-02 5:10 dpdklab
2026-01-01 8:09 dpdklab
2026-01-01 6:13 dpdklab
2026-01-01 5:47 dpdklab
2026-01-01 5:12 dpdklab
2025-12-31 7:23 dpdklab
2025-12-31 6:08 dpdklab
2025-12-31 5:10 dpdklab
2025-12-30 6:40 dpdklab
2025-12-30 5:12 dpdklab
2025-12-30 5:08 dpdklab
2025-12-29 7:33 dpdklab
2025-12-29 6:08 dpdklab
2025-12-29 5:09 dpdklab
2025-12-28 6:38 dpdklab
2025-12-28 6:10 dpdklab
2025-12-28 5:48 dpdklab
2025-12-28 5:09 dpdklab
2025-12-27 6:08 dpdklab
2025-12-27 5:52 dpdklab
2025-12-27 5:29 dpdklab
2025-12-27 5:09 dpdklab
2025-12-26 8:10 dpdklab
2025-12-26 7:19 dpdklab
2025-12-26 6:10 dpdklab
2025-12-26 5:10 dpdklab
2025-12-25 6:04 dpdklab
2025-12-25 5:09 dpdklab
2025-12-24 8:03 dpdklab
2025-12-24 6:15 dpdklab
2025-12-24 5:55 dpdklab
2025-12-24 5:11 dpdklab
2025-12-23 8:20 dpdklab
2025-12-23 6:19 dpdklab
2025-12-23 5:46 dpdklab
2025-12-23 5:12 dpdklab
2025-12-22 7:48 dpdklab
2025-12-22 7:34 dpdklab
2025-12-22 6:06 dpdklab
2025-12-22 5:11 dpdklab
2025-12-21 7:03 dpdklab
2025-12-21 5:17 dpdklab
2025-12-21 5:11 dpdklab
2025-12-20 7:35 dpdklab
2025-12-20 6:19 dpdklab
2025-12-20 5:09 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=69648513.050a0220.1932aa.1603SMTPIN_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).