From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 92d644f1d58838561d0996b2d4a9f5d276e41651
Date: Wed, 21 Feb 2024 15:23:22 -0800 (PST) [thread overview]
Message-ID: <65d685ea.050a0220.56230.fc92SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
92d644f1d58838561d0996b2d4a9f5d276e41651 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28089/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-21 23:23 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 23:23 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 21:24 dpdklab
2024-02-22 2:50 dpdklab
2024-02-22 1:17 dpdklab
2024-02-22 1:12 dpdklab
2024-02-22 0:58 dpdklab
2024-02-22 0:57 dpdklab
2024-02-22 0:50 dpdklab
2024-02-22 0:49 dpdklab
2024-02-22 0:43 dpdklab
2024-02-22 0:42 dpdklab
2024-02-22 0:24 dpdklab
2024-02-22 0:13 dpdklab
2024-02-22 0:06 dpdklab
2024-02-21 23:59 dpdklab
2024-02-21 23:50 dpdklab
2024-02-21 23:48 dpdklab
2024-02-21 23:43 dpdklab
2024-02-21 23:42 dpdklab
2024-02-21 23:39 dpdklab
2024-02-21 23:37 dpdklab
2024-02-21 23:34 dpdklab
2024-02-21 23:34 dpdklab
2024-02-21 23:33 dpdklab
2024-02-21 23:32 dpdklab
2024-02-21 23:30 dpdklab
2024-02-21 23:28 dpdklab
2024-02-21 23:26 dpdklab
2024-02-21 23:25 dpdklab
2024-02-21 23:22 dpdklab
2024-02-21 23:22 dpdklab
2024-02-21 23:21 dpdklab
2024-02-21 23:19 dpdklab
2024-02-21 23:00 dpdklab
2024-02-21 22:57 dpdklab
2024-02-21 22:55 dpdklab
2024-02-21 22:54 dpdklab
2024-02-21 22:51 dpdklab
2024-02-21 22:49 dpdklab
2024-02-21 22:47 dpdklab
2024-02-21 22:45 dpdklab
2024-02-21 22:45 dpdklab
2024-02-21 22:44 dpdklab
2024-02-21 22:41 dpdklab
2024-02-21 22:37 dpdklab
2024-02-21 22:37 dpdklab
2024-02-21 22:37 dpdklab
2024-02-21 22:35 dpdklab
2024-02-21 22:32 dpdklab
2024-02-21 22:28 dpdklab
2024-02-21 22:28 dpdklab
2024-02-21 22:24 dpdklab
2024-02-21 22:21 dpdklab
2024-02-21 22:16 dpdklab
2024-02-21 22:09 dpdklab
2024-02-21 22:09 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=65d685ea.050a0220.56230.fc92SMTPIN_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).