From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] 249c34811d8f134110784872ee3f31ead1fde84c
Date: Mon, 08 Jul 2024 00:32:01 -0700 (PDT) [thread overview]
Message-ID: <668b95f1.170a0220.b80ca.92adSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: dpdk-next-net
249c34811d8f134110784872ee3f31ead1fde84c --> testing pending
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 | PASS |
+---------------------+----------------------+--------------------+-------------------+
| FreeBSD 13.3 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| FreeBSD 14.1 | SKIPPED | PEND | 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 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/29767/
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-08 7:32 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 7:32 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-08 14:38 dpdklab
2024-07-08 14:34 dpdklab
2024-07-08 14:30 dpdklab
2024-07-08 14:17 dpdklab
2024-07-08 14:14 dpdklab
2024-07-08 14:11 dpdklab
2024-07-08 14:09 dpdklab
2024-07-08 14:07 dpdklab
2024-07-08 14:05 dpdklab
2024-07-08 14:00 dpdklab
2024-07-08 13:57 dpdklab
2024-07-08 13:53 dpdklab
2024-07-08 13:53 dpdklab
2024-07-08 13:52 dpdklab
2024-07-08 13:51 dpdklab
2024-07-08 13:48 dpdklab
2024-07-08 13:46 dpdklab
2024-07-08 13:42 dpdklab
2024-07-08 13:31 dpdklab
2024-07-08 13:30 dpdklab
2024-07-08 13:22 dpdklab
2024-07-08 13:18 dpdklab
2024-07-08 13:16 dpdklab
2024-07-08 13:14 dpdklab
2024-07-08 13:07 dpdklab
2024-07-08 13:04 dpdklab
2024-07-08 12:54 dpdklab
2024-07-08 12:52 dpdklab
2024-07-08 12:50 dpdklab
2024-07-08 12:46 dpdklab
2024-07-08 12:39 dpdklab
2024-07-08 12:37 dpdklab
2024-07-08 12:32 dpdklab
2024-07-08 12:27 dpdklab
2024-07-08 12:20 dpdklab
2024-07-08 12:15 dpdklab
2024-07-08 9:10 dpdklab
2024-07-08 8:26 dpdklab
2024-07-08 7:51 dpdklab
2024-07-08 7:50 dpdklab
2024-07-08 7:35 dpdklab
2024-07-08 7:34 dpdklab
2024-07-08 7:32 dpdklab
2024-07-08 7:31 dpdklab
2024-07-08 7:28 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=668b95f1.170a0220.b80ca.92adSMTPIN_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).