From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] f0d66a00ba66dc8581f33241f0a2d53c6741c58f
Date: Sat, 06 Jul 2024 03:58:46 -0700 (PDT) [thread overview]
Message-ID: <66892366.920a0220.c8500.d4b9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: dpdk-next-net
f0d66a00ba66dc8581f33241f0a2d53c6741c58f --> testing pending
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | PEND | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PEND | PEND |
+---------------------+--------------------+----------------------+
| FreeBSD 13.3 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 14.1 | 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/29751/
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-06 10:58 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 10:58 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-07 1:20 dpdklab
2024-07-07 1:17 dpdklab
2024-07-07 1:15 dpdklab
2024-07-07 1:15 dpdklab
2024-07-07 1:15 dpdklab
2024-07-07 1:13 dpdklab
2024-07-07 1:13 dpdklab
2024-07-07 1:11 dpdklab
2024-07-07 1:06 dpdklab
2024-07-07 1:04 dpdklab
2024-07-07 1:01 dpdklab
2024-07-07 0:58 dpdklab
2024-07-07 0:56 dpdklab
2024-07-07 0:55 dpdklab
2024-07-07 0:50 dpdklab
2024-07-07 0:48 dpdklab
2024-07-07 0:47 dpdklab
2024-07-07 0:44 dpdklab
2024-07-07 0:43 dpdklab
2024-07-06 21:01 dpdklab
2024-07-06 16:34 dpdklab
2024-07-06 16:33 dpdklab
2024-07-06 16:31 dpdklab
2024-07-06 16:29 dpdklab
2024-07-06 16:25 dpdklab
2024-07-06 16:23 dpdklab
2024-07-06 16:22 dpdklab
2024-07-06 16:21 dpdklab
2024-07-06 16:18 dpdklab
2024-07-06 16:17 dpdklab
2024-07-06 16:14 dpdklab
2024-07-06 16:10 dpdklab
2024-07-06 14:43 dpdklab
2024-07-06 13:38 dpdklab
2024-07-06 12:53 dpdklab
2024-07-06 12:05 dpdklab
2024-07-06 12:01 dpdklab
2024-07-06 11:48 dpdklab
2024-07-06 11:14 dpdklab
2024-07-06 11:06 dpdklab
2024-07-06 11:02 dpdklab
2024-07-06 11:02 dpdklab
2024-07-06 10:22 dpdklab
2024-07-06 8:43 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=66892366.920a0220.c8500.d4b9SMTPIN_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).