From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] c66daa12e76d7b4912cfb7109a761856a7a873ab
Date: Fri, 24 Jan 2025 22:41:21 -0800 (PST) [thread overview]
Message-ID: <67948791.050a0220.2b873e.afb9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: tags/v23.11
c66daa12e76d7b4912cfb7109a761856a7a873ab --> testing pending
Upstream job id: Windows-Compile-DPDK-VS#4729
Test environment and result as below:
+---------------------+-------------------+--------------------+
| Environment | dpdk_msvc_compile | dpdk_meson_compile |
+=====================+===================+====================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+-------------------+--------------------+
| FreeBSD 13.4 | SKIPPED | PEND |
+---------------------+-------------------+--------------------+
| FreeBSD 14.2 | SKIPPED | PEND |
+---------------------+-------------------+--------------------+
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
FreeBSD 13.4
Kernel: 13.4-RELEASE-p1
Compiler: clang 18.1.6
FreeBSD 14.2
Kernel: 14.2-RELEASE
Compiler: clang 18.1.6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/32343/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-01-25 6:41 UTC|newest]
Thread overview: 124+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 6:41 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-26 6:36 dpdklab
2025-01-26 6:10 dpdklab
2025-01-26 6:09 dpdklab
2025-01-26 5:59 dpdklab
2025-01-25 8:09 dpdklab
2025-01-25 7:06 dpdklab
2025-01-25 6:55 dpdklab
2025-01-24 20:14 dpdklab
2025-01-24 6:53 dpdklab
2025-01-24 6:14 dpdklab
2025-01-24 6:11 dpdklab
2025-01-24 6:02 dpdklab
2025-01-23 6:51 dpdklab
2025-01-23 6:30 dpdklab
2025-01-23 6:27 dpdklab
2025-01-23 6:17 dpdklab
2025-01-23 6:10 dpdklab
2025-01-22 6:58 dpdklab
2025-01-22 6:05 dpdklab
2025-01-22 5:35 dpdklab
2025-01-20 5:53 dpdklab
2025-01-19 6:08 dpdklab
2025-01-19 5:46 dpdklab
2025-01-19 5:40 dpdklab
2025-01-19 5:37 dpdklab
2025-01-19 5:35 dpdklab
2025-01-19 5:26 dpdklab
2025-01-18 6:43 dpdklab
2025-01-18 6:24 dpdklab
2025-01-18 6:08 dpdklab
2025-01-18 5:40 dpdklab
2025-01-17 7:44 dpdklab
2025-01-17 7:06 dpdklab
2025-01-17 7:00 dpdklab
2025-01-17 6:26 dpdklab
2025-01-16 7:06 dpdklab
2025-01-16 6:36 dpdklab
2025-01-16 6:31 dpdklab
2025-01-16 6:07 dpdklab
2025-01-16 5:43 dpdklab
2025-01-15 6:44 dpdklab
2025-01-15 6:42 dpdklab
2025-01-15 6:37 dpdklab
2025-01-14 7:25 dpdklab
2025-01-14 6:59 dpdklab
2025-01-14 6:35 dpdklab
2025-01-13 7:01 dpdklab
2025-01-13 6:31 dpdklab
2025-01-13 6:27 dpdklab
2025-01-13 6:01 dpdklab
2025-01-13 5:54 dpdklab
2025-01-12 6:42 dpdklab
2025-01-12 6:00 dpdklab
2025-01-12 5:36 dpdklab
2025-01-11 7:12 dpdklab
2025-01-11 6:47 dpdklab
2025-01-11 6:43 dpdklab
2025-01-11 6:18 dpdklab
2025-01-11 5:59 dpdklab
2025-01-10 7:25 dpdklab
2025-01-10 6:52 dpdklab
2025-01-10 6:33 dpdklab
2025-01-10 6:13 dpdklab
2025-01-10 5:47 dpdklab
2025-01-09 10:01 dpdklab
2025-01-09 9:13 dpdklab
2025-01-09 8:32 dpdklab
2025-01-09 3:54 dpdklab
2025-01-09 2:20 dpdklab
2025-01-09 2:03 dpdklab
2025-01-09 0:43 dpdklab
2025-01-07 9:11 dpdklab
2025-01-06 6:12 dpdklab
2025-01-06 5:46 dpdklab
2025-01-05 5:55 dpdklab
2025-01-05 5:50 dpdklab
2025-01-04 7:19 dpdklab
2025-01-04 7:01 dpdklab
2025-01-04 5:30 dpdklab
2025-01-03 7:59 dpdklab
2025-01-03 7:29 dpdklab
2025-01-03 7:02 dpdklab
2024-12-31 6:54 dpdklab
2024-12-31 6:16 dpdklab
2024-12-31 5:43 dpdklab
2024-12-30 7:18 dpdklab
2024-12-30 7:16 dpdklab
2024-12-30 6:55 dpdklab
2024-12-30 6:15 dpdklab
2024-12-30 5:44 dpdklab
2024-12-29 7:20 dpdklab
2024-12-29 6:18 dpdklab
2024-12-29 5:40 dpdklab
2024-12-28 7:46 dpdklab
2024-12-28 6:45 dpdklab
2024-12-27 6:37 dpdklab
2024-12-27 6:05 dpdklab
2024-12-27 5:36 dpdklab
2024-12-26 5:48 dpdklab
2024-12-25 7:27 dpdklab
2024-12-25 7:08 dpdklab
2024-12-25 6:48 dpdklab
2024-12-25 6:48 dpdklab
2024-12-25 5:59 dpdklab
2024-12-24 7:18 dpdklab
2024-12-24 7:05 dpdklab
2024-12-24 6:59 dpdklab
2024-12-24 5:46 dpdklab
2024-12-23 6:21 dpdklab
2024-12-23 5:55 dpdklab
2024-12-22 6:01 dpdklab
2024-12-22 5:50 dpdklab
2024-12-22 5:36 dpdklab
2024-12-22 5:14 dpdklab
2024-12-21 6:05 dpdklab
2024-12-21 5:35 dpdklab
2024-12-21 5:17 dpdklab
2024-12-20 6:50 dpdklab
2024-12-20 6:47 dpdklab
2024-12-20 6:25 dpdklab
2024-12-20 6:01 dpdklab
2024-12-19 7:12 dpdklab
2024-12-19 6:57 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=67948791.050a0220.2b873e.afb9SMTPIN_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).