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] 39d469a7eb4f157923be73aea0b0cc1015860ca7
Date: Tue, 14 Feb 2023 04:56:32 +0000 (UTC) [thread overview]
Message-ID: <20230214045632.800426009A@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]
_Testing PASS_
Branch: dpdk-next-crypto
39d469a7eb4f157923be73aea0b0cc1015860ca7 --> testing pass
Test environment and result as below:
+-------------------------------+----------------+
| Environment | dpdk_unit_test |
+===============================+================+
| Ubuntu 20.04 ARM GCC Native | PASS |
+-------------------------------+----------------+
| Ubuntu 20.04 ARM Clang Native | PASS |
+-------------------------------+----------------+
| Windows Server 2019 | PASS |
+-------------------------------+----------------+
| CentOS Stream 8 | PASS |
+-------------------------------+----------------+
| CentOS Stream 9 | PASS |
+-------------------------------+----------------+
| Debian Bullseye | PASS |
+-------------------------------+----------------+
| Debian Buster | PASS |
+-------------------------------+----------------+
| openSUSE Leap 15 | PASS |
+-------------------------------+----------------+
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/23308/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-14 4:56 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 4:56 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-17 21:05 dpdklab
2023-02-15 23:30 dpdklab
2023-02-14 16:41 dpdklab
2023-02-14 5:31 dpdklab
2023-02-14 5:31 dpdklab
2023-02-14 5:29 dpdklab
2023-02-14 5:25 dpdklab
2023-02-14 5:17 dpdklab
2023-02-14 5:04 dpdklab
2023-02-14 5:02 dpdklab
2023-02-14 4:58 dpdklab
2023-02-14 4:39 dpdklab
2023-02-14 4:36 dpdklab
2023-02-14 4:30 dpdklab
2023-02-13 18:41 dpdklab
2023-02-13 17:30 dpdklab
2023-02-13 17:18 dpdklab
2023-02-13 17:07 dpdklab
2023-02-13 16:55 dpdklab
2023-02-13 16:55 dpdklab
2023-02-13 16:50 dpdklab
2023-02-13 16:49 dpdklab
2023-02-13 16:44 dpdklab
2023-02-13 16:39 dpdklab
2023-02-13 7:45 dpdklab
2023-02-12 23:16 dpdklab
2023-02-12 22:31 dpdklab
2023-02-11 1:54 dpdklab
2023-02-11 0:49 dpdklab
2023-02-10 23:22 dpdklab
2023-02-10 23:18 dpdklab
2023-02-10 23:10 dpdklab
2023-02-10 23:10 dpdklab
2023-02-10 23:08 dpdklab
2023-02-10 23:06 dpdklab
2023-02-10 23:02 dpdklab
2023-02-10 23:02 dpdklab
2023-02-10 23:02 dpdklab
2023-02-10 23:01 dpdklab
2023-02-10 22:58 dpdklab
2023-02-10 22:53 dpdklab
2023-02-10 22:51 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=20230214045632.800426009A@dpdk-ubuntu.dpdklab.iol.unh.edu \
--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).