From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] 3317515e9377c13e458e31a64f8987a9d1f2eaf6
Date: Thu, 18 Jul 2024 02:07:54 -0700 (PDT) [thread overview]
Message-ID: <6698db6a.050a0220.132ea.a626SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: dpdk-next-net
3317515e9377c13e458e31a64f8987a9d1f2eaf6 --> testing pending
Upstream job id: Generic-VM-DPDK-Compile-Meson#28046
Test environment and result as below:
+---------------------+----------------------+--------------------+-------------------+
| Environment | dpdk_mingw64_compile | dpdk_meson_compile | dpdk_msvc_compile |
+=====================+======================+====================+===================+
| Windows Server 2022 | PASS | PEND | PEND |
+---------------------+----------------------+--------------------+-------------------+
| FreeBSD 13.3 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| FreeBSD 14.1 | SKIPPED | PEND | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
FreeBSD 13.3
Kernel: 13.3-RELEASE-p1
Compiler: clang 17.0.6
FreeBSD 14.1
Kernel: 14.1
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29898/
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-18 9:07 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 9:07 dpdklab [this message]
2024-07-18 9:08 dpdklab
2024-07-18 9:14 dpdklab
2024-07-18 9:17 dpdklab
2024-07-18 9:21 dpdklab
2024-07-18 9:27 dpdklab
2024-07-18 9:29 dpdklab
2024-07-18 9:29 dpdklab
2024-07-18 9:33 dpdklab
2024-07-18 9:33 dpdklab
2024-07-18 9:34 dpdklab
2024-07-18 9:36 dpdklab
2024-07-18 9:37 dpdklab
2024-07-18 9:44 dpdklab
2024-07-18 9:45 dpdklab
2024-07-18 9:53 dpdklab
2024-07-18 9:56 dpdklab
2024-07-18 9:58 dpdklab
2024-07-18 9:59 dpdklab
2024-07-18 10:00 dpdklab
2024-07-18 10:04 dpdklab
2024-07-18 10:09 dpdklab
2024-07-18 11:40 dpdklab
2024-07-18 11:42 dpdklab
2024-07-18 11:43 dpdklab
2024-07-18 11:45 dpdklab
2024-07-18 11:49 dpdklab
2024-07-18 11:49 dpdklab
2024-07-18 11:51 dpdklab
2024-07-18 11:53 dpdklab
2024-07-18 11:56 dpdklab
2024-07-18 11:58 dpdklab
2024-07-18 11:58 dpdklab
2024-07-18 12:00 dpdklab
2024-07-18 12:03 dpdklab
2024-07-18 12:04 dpdklab
2024-07-18 12:06 dpdklab
2024-07-18 12:06 dpdklab
2024-07-18 12:08 dpdklab
2024-07-18 12:08 dpdklab
2024-07-18 12:08 dpdklab
2024-07-18 12:08 dpdklab
2024-07-18 12:08 dpdklab
2024-07-18 12:09 dpdklab
2024-07-18 12:09 dpdklab
2024-07-18 12:11 dpdklab
2024-07-18 12:12 dpdklab
2024-07-18 12:14 dpdklab
2024-07-18 12:15 dpdklab
2024-07-18 12:19 dpdklab
2024-07-18 12:21 dpdklab
2024-07-18 12:24 dpdklab
2024-07-18 12:28 dpdklab
2024-07-18 12:29 dpdklab
2024-07-18 12:32 dpdklab
2024-07-18 12:34 dpdklab
2024-07-18 12:37 dpdklab
2024-07-18 12:38 dpdklab
2024-07-18 12:40 dpdklab
2024-07-18 12:41 dpdklab
2024-07-18 12:41 dpdklab
2024-07-18 12:42 dpdklab
2024-07-18 12:45 dpdklab
2024-07-18 12:50 dpdklab
2024-07-18 12:55 dpdklab
2024-07-18 12:56 dpdklab
2024-07-18 12:56 dpdklab
2024-07-18 13:09 dpdklab
2024-07-18 13:21 dpdklab
2024-07-18 13:30 dpdklab
2024-07-18 13:32 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=6698db6a.050a0220.132ea.a626SMTPIN_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).