From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 93998f3c5f22747e4f2c5e8714fa5cbe6c9d1574
Date: Sat, 17 Feb 2024 17:30:39 -0800 (PST) [thread overview]
Message-ID: <65d15dbf.810a0220.9bbbf.4e61SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
93998f3c5f22747e4f2c5e8714fa5cbe6c9d1574 --> 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 |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Alpine | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | 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
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28042/
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-18 1:30 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 1:30 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-18 3:13 dpdklab
2024-02-18 3:09 dpdklab
2024-02-18 2:47 dpdklab
2024-02-18 2:20 dpdklab
2024-02-18 2:19 dpdklab
2024-02-18 2:11 dpdklab
2024-02-18 2:04 dpdklab
2024-02-18 2:04 dpdklab
2024-02-18 2:01 dpdklab
2024-02-18 1:58 dpdklab
2024-02-18 1:57 dpdklab
2024-02-18 1:57 dpdklab
2024-02-18 1:54 dpdklab
2024-02-18 1:53 dpdklab
2024-02-18 1:53 dpdklab
2024-02-18 1:51 dpdklab
2024-02-18 1:47 dpdklab
2024-02-18 1:44 dpdklab
2024-02-18 1:43 dpdklab
2024-02-18 1:43 dpdklab
2024-02-18 1:42 dpdklab
2024-02-18 1:42 dpdklab
2024-02-18 1:41 dpdklab
2024-02-18 1:41 dpdklab
2024-02-18 1:41 dpdklab
2024-02-18 1:40 dpdklab
2024-02-18 1:40 dpdklab
2024-02-18 1:37 dpdklab
2024-02-18 1:36 dpdklab
2024-02-18 1:36 dpdklab
2024-02-18 1:36 dpdklab
2024-02-18 1:35 dpdklab
2024-02-18 1:34 dpdklab
2024-02-18 1:34 dpdklab
2024-02-18 1:34 dpdklab
2024-02-18 1:33 dpdklab
2024-02-18 1:30 dpdklab
2024-02-18 1:30 dpdklab
2024-02-18 1:29 dpdklab
2024-02-18 1:29 dpdklab
2024-02-18 1:28 dpdklab
2024-02-18 1:26 dpdklab
2024-02-18 1:26 dpdklab
2024-02-18 1:25 dpdklab
2024-02-18 1:25 dpdklab
2024-02-18 1:25 dpdklab
2024-02-18 1:24 dpdklab
2024-02-18 1:24 dpdklab
2024-02-18 1:24 dpdklab
2024-02-18 1:24 dpdklab
2024-02-18 1:23 dpdklab
2024-02-18 1:23 dpdklab
2024-02-18 1:22 dpdklab
2024-02-18 1: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=65d15dbf.810a0220.9bbbf.4e61SMTPIN_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).