From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 7f82e9c89f3514715533feb34f46ff1ea95c6f98
Date: Sun, 17 Mar 2024 13:12:09 -0700 (PDT) [thread overview]
Message-ID: <65f74e99.170a0220.79f28.995aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-crypto
7f82e9c89f3514715533feb34f46ff1ea95c6f98 --> testing pass
Test environment and result as below:
+---------------------+--------------------+
| Environment | dpdk_meson_compile |
+=====================+====================+
| Debian Bullseye | PASS |
+---------------------+--------------------+
| Debian 12 (arm) | PASS |
+---------------------+--------------------+
| Fedora 37 | PASS |
+---------------------+--------------------+
| Fedora 38 | PASS |
+---------------------+--------------------+
| Windows Server 2022 | PASS |
+---------------------+--------------------+
| FreeBSD 13.2 | PASS |
+---------------------+--------------------+
| CentOS Stream 9 | PASS |
+---------------------+--------------------+
| Ubuntu 20.04 | PASS |
+---------------------+--------------------+
| Ubuntu 22.04 | PASS |
+---------------------+--------------------+
| CentOS Stream 8 | PASS |
+---------------------+--------------------+
| RHEL8 | PASS |
+---------------------+--------------------+
| openSUSE Leap 15 | PASS |
+---------------------+--------------------+
| Alpine | PASS |
+---------------------+--------------------+
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Alpine
Kernel: 5.4.0-167-generic
Compiler: gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28519/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-03-17 20:12 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 20:12 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-20 3:16 dpdklab
2024-03-20 2:40 dpdklab
2024-03-19 21:01 dpdklab
2024-03-19 20:16 dpdklab
2024-03-17 21:29 dpdklab
2024-03-17 20:36 dpdklab
2024-03-17 20:33 dpdklab
2024-03-17 20:28 dpdklab
2024-03-17 20:26 dpdklab
2024-03-17 20:25 dpdklab
2024-03-17 20:24 dpdklab
2024-03-17 20:22 dpdklab
2024-03-17 20:21 dpdklab
2024-03-17 20:20 dpdklab
2024-03-17 20:17 dpdklab
2024-03-17 20:17 dpdklab
2024-03-17 20:17 dpdklab
2024-03-17 20:17 dpdklab
2024-03-17 20:16 dpdklab
2024-03-17 20:16 dpdklab
2024-03-17 20:16 dpdklab
2024-03-17 20:16 dpdklab
2024-03-17 20:15 dpdklab
2024-03-17 20:15 dpdklab
2024-03-17 20:15 dpdklab
2024-03-17 20:15 dpdklab
2024-03-17 20:14 dpdklab
2024-03-17 20:14 dpdklab
2024-03-17 20:14 dpdklab
2024-03-17 20:14 dpdklab
2024-03-17 20:13 dpdklab
2024-03-17 20:13 dpdklab
2024-03-17 20:13 dpdklab
2024-03-17 20:12 dpdklab
2024-03-17 20:12 dpdklab
2024-03-17 20:11 dpdklab
2024-03-17 20:11 dpdklab
2024-03-17 20:11 dpdklab
2024-03-17 20:10 dpdklab
2024-03-17 20:10 dpdklab
2024-03-17 20:10 dpdklab
2024-03-17 20:10 dpdklab
2024-03-17 20:10 dpdklab
2024-03-17 20:10 dpdklab
2024-03-17 20:08 dpdklab
2024-03-17 20:08 dpdklab
2024-03-17 20:08 dpdklab
2024-03-17 20:08 dpdklab
2024-03-17 20:08 dpdklab
2024-03-17 20:07 dpdklab
2024-03-17 20:05 dpdklab
2024-03-16 17:10 dpdklab
2024-03-16 16:31 dpdklab
2024-03-16 16:15 dpdklab
2024-03-16 16:15 dpdklab
2024-03-16 16:10 dpdklab
2024-03-16 16:10 dpdklab
2024-03-16 16:09 dpdklab
2024-03-16 16:08 dpdklab
2024-03-16 16:08 dpdklab
2024-03-16 16:07 dpdklab
2024-03-16 16:07 dpdklab
2024-03-16 16:07 dpdklab
2024-03-16 16:06 dpdklab
2024-03-16 16:06 dpdklab
2024-03-16 16:05 dpdklab
2024-03-16 16:04 dpdklab
2024-03-16 16:04 dpdklab
2024-03-16 16:03 dpdklab
2024-03-16 16:03 dpdklab
2024-03-16 16:02 dpdklab
2024-03-16 16:02 dpdklab
2024-03-16 16:02 dpdklab
2024-03-16 16:01 dpdklab
2024-03-16 16:01 dpdklab
2024-03-16 15:59 dpdklab
2024-03-16 15:59 dpdklab
2024-03-16 15:59 dpdklab
2024-03-16 15:58 dpdklab
2024-03-16 15:58 dpdklab
2024-03-16 15:58 dpdklab
2024-03-16 15:58 dpdklab
2024-03-16 15:58 dpdklab
2024-03-16 15:57 dpdklab
2024-03-16 15:57 dpdklab
2024-03-16 15:57 dpdklab
2024-03-16 15:57 dpdklab
2024-03-16 15:56 dpdklab
2024-03-16 15:56 dpdklab
2024-03-16 15:56 dpdklab
2024-03-16 15:56 dpdklab
2024-03-16 15:56 dpdklab
2024-03-16 15:56 dpdklab
2024-03-16 15:55 dpdklab
2024-03-16 15:55 dpdklab
2024-03-16 15:55 dpdklab
2024-03-16 15:55 dpdklab
2024-03-16 15:55 dpdklab
2024-03-16 15:55 dpdklab
2024-03-16 15:54 dpdklab
2024-03-16 15:54 dpdklab
2024-03-16 15:54 dpdklab
2024-03-16 15:54 dpdklab
2024-03-16 15:54 dpdklab
2024-03-16 15:54 dpdklab
2024-03-16 15:54 dpdklab
2024-03-16 15:54 dpdklab
2024-03-16 15:53 dpdklab
2024-03-16 15:53 dpdklab
2024-03-16 15:53 dpdklab
2024-03-16 15:53 dpdklab
2024-03-16 15:53 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=65f74e99.170a0220.79f28.995aSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=gakhil@marvell.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).