From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] a6bbf008457a455fcf4cf7374c280bba697a353f
Date: Wed, 05 Jun 2024 00:17:49 -0700 (PDT) [thread overview]
Message-ID: <6660111d.050a0220.36b5e.80b1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
a6bbf008457a455fcf4cf7374c280bba697a353f --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+-------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| FreeBSD 13.3 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 14.0 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2019 | PASS | PASS | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PASS | PASS | PASS |
+---------------------+--------------------+----------------------+-------------------+
FreeBSD 13.3
Kernel: 13.3-RELEASE-p1
Compiler: clang 17.0.6
FreeBSD 14.0
Kernel: 14.0
Compiler: clang 16.0.6
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29338/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-06-05 7:17 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 7:17 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-05 21:47 dpdklab
2024-06-05 21:43 dpdklab
2024-06-05 21:18 dpdklab
2024-06-05 21:17 dpdklab
2024-06-05 10:46 dpdklab
2024-06-05 9:09 dpdklab
2024-06-05 9:08 dpdklab
2024-06-05 9:08 dpdklab
2024-06-05 9:07 dpdklab
2024-06-05 9:06 dpdklab
2024-06-05 9:04 dpdklab
2024-06-05 9:03 dpdklab
2024-06-05 9:03 dpdklab
2024-06-05 9:02 dpdklab
2024-06-05 9:02 dpdklab
2024-06-05 9:02 dpdklab
2024-06-05 9:02 dpdklab
2024-06-05 9:01 dpdklab
2024-06-05 8:59 dpdklab
2024-06-05 8:53 dpdklab
2024-06-05 8:52 dpdklab
2024-06-05 8:51 dpdklab
2024-06-05 8:51 dpdklab
2024-06-05 8:50 dpdklab
2024-06-05 8:50 dpdklab
2024-06-05 8:49 dpdklab
2024-06-05 8:48 dpdklab
2024-06-05 8:42 dpdklab
2024-06-05 8:28 dpdklab
2024-06-05 8:25 dpdklab
2024-06-05 8:24 dpdklab
2024-06-05 8:23 dpdklab
2024-06-05 8:22 dpdklab
2024-06-05 8:21 dpdklab
2024-06-05 8:21 dpdklab
2024-06-05 8:19 dpdklab
2024-06-05 8:16 dpdklab
2024-06-05 8:16 dpdklab
2024-06-05 8:14 dpdklab
2024-06-05 8:13 dpdklab
2024-06-05 8:13 dpdklab
2024-06-05 8:10 dpdklab
2024-06-05 7:58 dpdklab
2024-06-05 7:46 dpdklab
2024-06-05 7:44 dpdklab
2024-06-05 7:40 dpdklab
2024-06-05 7:40 dpdklab
2024-06-05 7:39 dpdklab
2024-06-05 7:39 dpdklab
2024-06-05 7:38 dpdklab
2024-06-05 7:37 dpdklab
2024-06-05 7:35 dpdklab
2024-06-05 7:34 dpdklab
2024-06-05 7:34 dpdklab
2024-06-05 7:34 dpdklab
2024-06-05 7:33 dpdklab
2024-06-05 7:31 dpdklab
2024-06-05 7:31 dpdklab
2024-06-05 7:30 dpdklab
2024-06-05 7:30 dpdklab
2024-06-05 7:27 dpdklab
2024-06-05 7:27 dpdklab
2024-06-05 7:26 dpdklab
2024-06-05 7:25 dpdklab
2024-06-05 7:24 dpdklab
2024-06-05 7:23 dpdklab
2024-06-05 7:23 dpdklab
2024-06-05 7:22 dpdklab
2024-06-05 7:22 dpdklab
2024-06-05 7:20 dpdklab
2024-06-05 7:18 dpdklab
2024-06-05 7:16 dpdklab
2024-06-05 7:16 dpdklab
2024-06-05 6:57 dpdklab
2024-06-05 6:56 dpdklab
2024-06-05 6:55 dpdklab
2024-06-05 6:55 dpdklab
2024-06-05 6:54 dpdklab
2024-06-05 6:53 dpdklab
2024-06-05 6:53 dpdklab
2024-06-05 6:52 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=6660111d.050a0220.36b5e.80b1SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.com \
--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).