From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| [GIT MASTER] c581c49cd3fcaff596fbe566e270b442e6326c79
Date: Fri, 9 Dec 2022 19:38:47 +0000 (UTC) [thread overview]
Message-ID: <20221209193847.146386052E@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2118 bytes --]
_Testing PASS_
Branch: dpdk-next-crypto
c581c49cd3fcaff596fbe566e270b442e6326c79 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| RHEL 7 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
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
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 12.2.1-2
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/22593/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-12-09 19:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 19:38 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-09 20:15 dpdklab
2022-12-09 19:38 dpdklab
2022-12-09 19:23 dpdklab
2022-12-09 19:11 dpdklab
2022-12-09 19:09 dpdklab
2022-12-09 19:08 dpdklab
2022-12-09 19:07 dpdklab
2022-12-09 19:07 dpdklab
2022-12-09 19:07 dpdklab
2022-12-09 18:32 dpdklab
2022-12-09 17:08 dpdklab
2022-12-09 17:04 dpdklab
2022-12-09 16:49 dpdklab
2022-12-09 16:48 dpdklab
2022-12-09 16:48 dpdklab
2022-12-09 16:43 dpdklab
2022-12-09 1:05 dpdklab
2022-12-09 1:05 dpdklab
2022-12-09 1:05 dpdklab
2022-12-09 1:04 dpdklab
2022-12-09 1:04 dpdklab
2022-12-09 1:04 dpdklab
2022-12-09 0:44 dpdklab
2022-12-09 0:43 dpdklab
2022-12-09 0:43 dpdklab
2022-12-09 0:22 dpdklab
2022-12-08 23:53 dpdklab
2022-12-08 23:18 dpdklab
2022-12-08 23:10 dpdklab
2022-12-08 23:05 dpdklab
2022-12-08 23:04 dpdklab
2022-12-08 22:57 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=20221209193847.146386052E@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@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).