From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] 9cad88310860ad99f9133af39f9cf98e524de9ac
Date: Tue, 23 Jul 2024 23:45:51 -0700 (PDT) [thread overview]
Message-ID: <66a0a31f.630a0220.c955a.3d0bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: dpdk-next-net
9cad88310860ad99f9133af39f9cf98e524de9ac --> testing pending
Upstream job id: Windows-Compile-DPDK-Meson#23796
Test environment and result as below:
+---------------------+----------------------+--------------------+-------------------+
| Environment | dpdk_mingw64_compile | dpdk_meson_compile | dpdk_msvc_compile |
+=====================+======================+====================+===================+
| Windows Server 2019 | PASS | PEND | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| Windows Server 2022 | PEND | PASS | PEND |
+---------------------+----------------------+--------------------+-------------------+
| FreeBSD 14.1 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
FreeBSD 14.1
Kernel: 14.1
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29980/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-07-24 7:59 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 6:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-24 9:15 dpdklab
2024-07-24 9:15 dpdklab
2024-07-24 9:14 dpdklab
2024-07-24 9:13 dpdklab
2024-07-24 9:11 dpdklab
2024-07-24 9:09 dpdklab
2024-07-24 9:07 dpdklab
2024-07-24 9:07 dpdklab
2024-07-24 9:02 dpdklab
2024-07-24 8:58 dpdklab
2024-07-24 8:57 dpdklab
2024-07-24 8:56 dpdklab
2024-07-24 8:54 dpdklab
2024-07-24 8:53 dpdklab
2024-07-24 8:46 dpdklab
2024-07-24 8:46 dpdklab
2024-07-24 8:35 dpdklab
2024-07-24 7:58 dpdklab
2024-07-24 7:54 dpdklab
2024-07-24 7:54 dpdklab
2024-07-24 7:48 dpdklab
2024-07-24 7:48 dpdklab
2024-07-24 7:46 dpdklab
2024-07-24 7:45 dpdklab
2024-07-24 7:45 dpdklab
2024-07-24 7:43 dpdklab
2024-07-24 7:42 dpdklab
2024-07-24 7:40 dpdklab
2024-07-24 7:40 dpdklab
2024-07-24 7:39 dpdklab
2024-07-24 7:38 dpdklab
2024-07-24 7:37 dpdklab
2024-07-24 7:36 dpdklab
2024-07-24 7:35 dpdklab
2024-07-24 7:35 dpdklab
2024-07-24 7:33 dpdklab
2024-07-24 7:32 dpdklab
2024-07-24 7:32 dpdklab
2024-07-24 7:31 dpdklab
2024-07-24 7:31 dpdklab
2024-07-24 7:30 dpdklab
2024-07-24 7:30 dpdklab
2024-07-24 7:24 dpdklab
2024-07-24 7:24 dpdklab
2024-07-24 7:24 dpdklab
2024-07-24 7:24 dpdklab
2024-07-24 7:23 dpdklab
2024-07-24 7:23 dpdklab
2024-07-24 7:21 dpdklab
2024-07-24 7:14 dpdklab
2024-07-24 7:14 dpdklab
2024-07-24 7:08 dpdklab
2024-07-24 7:06 dpdklab
2024-07-24 7:06 dpdklab
2024-07-24 7:03 dpdklab
2024-07-24 7:02 dpdklab
2024-07-24 7:02 dpdklab
2024-07-24 6:53 dpdklab
2024-07-24 6:52 dpdklab
2024-07-24 6:51 dpdklab
2024-07-24 6:51 dpdklab
2024-07-24 6:51 dpdklab
2024-07-24 6:45 dpdklab
2024-07-24 6:43 dpdklab
2024-07-24 6:43 dpdklab
2024-07-24 6:42 dpdklab
2024-07-24 6:42 dpdklab
2024-07-24 6:40 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=66a0a31f.630a0220.c955a.3d0bSMTPIN_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).