From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] 3f091744e940ca7e93309fc23224cc5208c590eb
Date: Mon, 01 Jul 2024 05:28:02 -0700 (PDT) [thread overview]
Message-ID: <6682a0d2.050a0220.fb0a7.9f04SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: dpdk-next-net-intel
3f091744e940ca7e93309fc23224cc5208c590eb --> 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 | PASS | PASS |
+---------------------+--------------------+----------------------+-------------------+
| 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/29658/
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-01 12:28 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 12:28 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-01 15:32 dpdklab
2024-07-01 15:31 dpdklab
2024-07-01 15:29 dpdklab
2024-07-01 15:24 dpdklab
2024-07-01 15:22 dpdklab
2024-07-01 15:15 dpdklab
2024-07-01 15:08 dpdklab
2024-07-01 15:01 dpdklab
2024-07-01 14:59 dpdklab
2024-07-01 14:51 dpdklab
2024-07-01 14:36 dpdklab
2024-07-01 14:34 dpdklab
2024-07-01 14:33 dpdklab
2024-07-01 14:27 dpdklab
2024-07-01 14:26 dpdklab
2024-07-01 14:26 dpdklab
2024-07-01 14:25 dpdklab
2024-07-01 14:25 dpdklab
2024-07-01 14:19 dpdklab
2024-07-01 14:19 dpdklab
2024-07-01 14:18 dpdklab
2024-07-01 14:18 dpdklab
2024-07-01 14:17 dpdklab
2024-07-01 14:16 dpdklab
2024-07-01 14:14 dpdklab
2024-07-01 14:13 dpdklab
2024-07-01 14:12 dpdklab
2024-07-01 14:10 dpdklab
2024-07-01 14:09 dpdklab
2024-07-01 14:08 dpdklab
2024-07-01 14:06 dpdklab
2024-07-01 14:06 dpdklab
2024-07-01 14:05 dpdklab
2024-07-01 14:03 dpdklab
2024-07-01 13:59 dpdklab
2024-07-01 13:57 dpdklab
2024-07-01 13:56 dpdklab
2024-07-01 13:56 dpdklab
2024-07-01 13:54 dpdklab
2024-07-01 13:54 dpdklab
2024-07-01 13:53 dpdklab
2024-07-01 13:52 dpdklab
2024-07-01 13:46 dpdklab
2024-07-01 13:44 dpdklab
2024-07-01 13:43 dpdklab
2024-07-01 13:42 dpdklab
2024-07-01 13:40 dpdklab
2024-07-01 13:40 dpdklab
2024-07-01 13:35 dpdklab
2024-07-01 13:35 dpdklab
2024-07-01 13:35 dpdklab
2024-07-01 13:33 dpdklab
2024-07-01 13:31 dpdklab
2024-07-01 13:31 dpdklab
2024-07-01 13:29 dpdklab
2024-07-01 13:27 dpdklab
2024-07-01 13:26 dpdklab
2024-07-01 13:26 dpdklab
2024-07-01 13:25 dpdklab
2024-07-01 13:23 dpdklab
2024-07-01 13:21 dpdklab
2024-07-01 13:16 dpdklab
2024-07-01 13:16 dpdklab
2024-07-01 13:15 dpdklab
2024-07-01 13:14 dpdklab
2024-07-01 13:13 dpdklab
2024-07-01 13:12 dpdklab
2024-07-01 13:11 dpdklab
2024-07-01 12:47 dpdklab
2024-07-01 12:27 dpdklab
2024-07-01 12:24 dpdklab
2024-07-01 12:23 dpdklab
2024-07-01 12:22 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=6682a0d2.050a0220.fb0a7.9f04SMTPIN_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).