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] 8f27705b70911d12dc0f356a728d73279fbc1e84
Date: Thu, 29 Feb 2024 19:20:38 -0800 (PST) [thread overview]
Message-ID: <65e14986.050a0220.d284a.811eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-crypto
8f27705b70911d12dc0f356a728d73279fbc1e84 --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| CentOS Stream 9 | PASS |
+------------------+----------------+
| CentOS Stream 8 | PASS |
+------------------+----------------+
| RHEL8 | PASS |
+------------------+----------------+
| Debian 12 (arm) | PASS |
+------------------+----------------+
| Debian Bullseye | PASS |
+------------------+----------------+
| Fedora 37 | PASS |
+------------------+----------------+
| Fedora 38 | PASS |
+------------------+----------------+
| Ubuntu 20.04 | PASS |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
| Ubuntu 22.04 | PASS |
+------------------+----------------+
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
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
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
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28246/
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-01 3:20 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 3:20 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-04 7:53 dpdklab
2024-03-04 7:21 dpdklab
2024-03-04 7:01 dpdklab
2024-03-02 14:05 dpdklab
2024-03-01 13:48 dpdklab
2024-03-01 13:41 dpdklab
2024-03-01 13:34 dpdklab
2024-03-01 13:32 dpdklab
2024-03-01 8:48 dpdklab
2024-03-01 5:19 dpdklab
2024-03-01 5:18 dpdklab
2024-03-01 4:52 dpdklab
2024-03-01 4:33 dpdklab
2024-03-01 4:20 dpdklab
2024-03-01 4:19 dpdklab
2024-03-01 4:09 dpdklab
2024-03-01 4:09 dpdklab
2024-03-01 4:07 dpdklab
2024-03-01 4:06 dpdklab
2024-03-01 3:58 dpdklab
2024-03-01 3:57 dpdklab
2024-03-01 3:57 dpdklab
2024-03-01 3:56 dpdklab
2024-03-01 3:55 dpdklab
2024-03-01 3:54 dpdklab
2024-03-01 3:54 dpdklab
2024-03-01 3:53 dpdklab
2024-03-01 3:53 dpdklab
2024-03-01 3:52 dpdklab
2024-03-01 3:52 dpdklab
2024-03-01 3:52 dpdklab
2024-03-01 3:52 dpdklab
2024-03-01 3:52 dpdklab
2024-03-01 3:51 dpdklab
2024-03-01 3:51 dpdklab
2024-03-01 3:50 dpdklab
2024-03-01 3:50 dpdklab
2024-03-01 3:49 dpdklab
2024-03-01 3:49 dpdklab
2024-03-01 3:48 dpdklab
2024-03-01 3:48 dpdklab
2024-03-01 3:45 dpdklab
2024-03-01 3:41 dpdklab
2024-03-01 3:32 dpdklab
2024-03-01 3:32 dpdklab
2024-03-01 3:31 dpdklab
2024-03-01 3:30 dpdklab
2024-03-01 3:23 dpdklab
2024-03-01 3:22 dpdklab
2024-03-01 3:22 dpdklab
2024-03-01 3:22 dpdklab
2024-03-01 3:20 dpdklab
2024-03-01 3:17 dpdklab
2024-02-29 23:45 dpdklab
2024-02-29 23:43 dpdklab
2024-02-29 23:40 dpdklab
2024-02-29 23:38 dpdklab
2024-02-29 23:33 dpdklab
2024-02-29 23:21 dpdklab
2024-02-29 23:19 dpdklab
2024-02-29 23:11 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=65e14986.050a0220.d284a.811eSMTPIN_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).