From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] 8e8aa4a4f90dce1fcea03a93f508e3d9bc0c98c0
Date: Tue, 09 Jul 2024 17:30:46 -0700 (PDT) [thread overview]
Message-ID: <668dd636.050a0220.8a9c4.6c37SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: dpdk
8e8aa4a4f90dce1fcea03a93f508e3d9bc0c98c0 --> testing pending
Test environment and result as below:
+---------------------+--------------------+----------------------+-------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| Windows Server 2019 | PASS | PEND | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PASS | PEND | PEND |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 13.3 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 14.1 | PASS | SKIPPED | 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/29795/
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-10 0:30 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 0:30 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-10 8:17 dpdklab
2024-07-10 7:27 dpdklab
2024-07-10 7:24 dpdklab
2024-07-10 7:21 dpdklab
2024-07-10 7:18 dpdklab
2024-07-10 7:14 dpdklab
2024-07-10 7:13 dpdklab
2024-07-10 7:07 dpdklab
2024-07-10 7:06 dpdklab
2024-07-10 7:00 dpdklab
2024-07-10 6:58 dpdklab
2024-07-10 6:55 dpdklab
2024-07-10 6:54 dpdklab
2024-07-10 6:54 dpdklab
2024-07-10 6:47 dpdklab
2024-07-10 6:41 dpdklab
2024-07-10 6:39 dpdklab
2024-07-10 6:38 dpdklab
2024-07-10 6:36 dpdklab
2024-07-10 6:35 dpdklab
2024-07-10 6:32 dpdklab
2024-07-10 6:31 dpdklab
2024-07-10 6:30 dpdklab
2024-07-10 6:30 dpdklab
2024-07-10 6:29 dpdklab
2024-07-10 6:27 dpdklab
2024-07-10 6:27 dpdklab
2024-07-10 6:26 dpdklab
2024-07-10 6:25 dpdklab
2024-07-10 6:23 dpdklab
2024-07-10 6:22 dpdklab
2024-07-10 6:21 dpdklab
2024-07-10 6:18 dpdklab
2024-07-10 6:16 dpdklab
2024-07-10 6:14 dpdklab
2024-07-10 6:11 dpdklab
2024-07-10 6:07 dpdklab
2024-07-10 6:05 dpdklab
2024-07-10 5:57 dpdklab
2024-07-10 5:56 dpdklab
2024-07-10 5:54 dpdklab
2024-07-10 5:48 dpdklab
2024-07-10 5:46 dpdklab
2024-07-10 5:44 dpdklab
2024-07-10 5:43 dpdklab
2024-07-10 5:41 dpdklab
2024-07-10 5:37 dpdklab
2024-07-10 5:37 dpdklab
2024-07-10 1:17 dpdklab
2024-07-10 1:16 dpdklab
2024-07-10 1:14 dpdklab
2024-07-10 1:12 dpdklab
2024-07-10 1:10 dpdklab
2024-07-10 1:06 dpdklab
2024-07-10 1:06 dpdklab
2024-07-10 1:03 dpdklab
2024-07-10 1:01 dpdklab
2024-07-10 0:59 dpdklab
2024-07-10 0:58 dpdklab
2024-07-10 0:50 dpdklab
2024-07-10 0:50 dpdklab
2024-07-10 0:48 dpdklab
2024-07-10 0:48 dpdklab
2024-07-10 0:47 dpdklab
2024-07-10 0:46 dpdklab
2024-07-10 0:45 dpdklab
2024-07-10 0:42 dpdklab
2024-07-10 0:37 dpdklab
2024-07-10 0:35 dpdklab
2024-07-10 0:35 dpdklab
2024-07-10 0:34 dpdklab
2024-07-10 0:31 dpdklab
2024-07-10 0:31 dpdklab
2024-07-10 0:27 dpdklab
2024-07-10 0:21 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=668dd636.050a0220.8a9c4.6c37SMTPIN_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).