From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 3b3af56d3c9c472f9ba0ee1078d714919cc2b6b4
Date: Mon, 27 Nov 2023 17:57:53 -0800 (PST) [thread overview]
Message-ID: <65654921.250a0220.e44ed.8135SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
3b3af56d3c9c472f9ba0ee1078d714919cc2b6b4 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | SKIPPED | PASS |
+---------------------+--------------------+----------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27136/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-28 1:57 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 1:57 dpdklab [this message]
2023-11-28 1:58 dpdklab
2023-11-28 1:58 dpdklab
2023-11-28 1:58 dpdklab
2023-11-28 1:59 dpdklab
2023-11-28 2:00 dpdklab
2023-11-28 2:01 dpdklab
2023-11-28 2:02 dpdklab
2023-11-28 2:02 dpdklab
2023-11-28 2:02 dpdklab
2023-11-28 2:02 dpdklab
2023-11-28 2:02 dpdklab
2023-11-28 2:02 dpdklab
2023-11-28 2:03 dpdklab
2023-11-28 2:03 dpdklab
2023-11-28 2:03 dpdklab
2023-11-28 2:03 dpdklab
2023-11-28 2:03 dpdklab
2023-11-28 2:05 dpdklab
2023-11-28 2:06 dpdklab
2023-11-28 2:06 dpdklab
2023-11-28 2:06 dpdklab
2023-11-28 2:06 dpdklab
2023-11-28 2:06 dpdklab
2023-11-28 2:06 dpdklab
2023-11-28 2:07 dpdklab
2023-11-28 2:09 dpdklab
2023-11-28 2:12 dpdklab
2023-11-28 2:12 dpdklab
2023-11-28 2:12 dpdklab
2023-11-28 2:12 dpdklab
2023-11-28 2:13 dpdklab
2023-11-28 2:14 dpdklab
2023-11-28 2:16 dpdklab
2023-11-28 2:16 dpdklab
2023-11-28 2:19 dpdklab
2023-11-28 2:20 dpdklab
2023-11-28 2:23 dpdklab
2023-11-28 2:23 dpdklab
2023-11-28 2:30 dpdklab
2023-11-28 2:31 dpdklab
2023-11-28 2:32 dpdklab
2023-11-28 2:37 dpdklab
2023-11-28 2:39 dpdklab
2023-11-28 2:40 dpdklab
2023-11-28 2:45 dpdklab
2023-11-28 2:51 dpdklab
2023-11-28 2:53 dpdklab
2023-11-28 3:03 dpdklab
2023-11-28 3:12 dpdklab
2023-11-28 3:27 dpdklab
2023-11-28 4:19 dpdklab
2023-11-28 5:29 dpdklab
2023-11-28 16:20 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=65654921.250a0220.e44ed.8135SMTPIN_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).