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] 3c464365f8c881863ca911631c0ab0aa18d62032
Date: Fri, 22 Mar 2024 15:24:50 -0700 (PDT) [thread overview]
Message-ID: <65fe0532.170a0220.32fd2.0dabSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-crypto
3c464365f8c881863ca911631c0ab0aa18d62032 --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| Debian Bullseye | PASS |
+------------------+----------------+
| CentOS Stream 8 | PASS |
+------------------+----------------+
| CentOS Stream 9 | PASS |
+------------------+----------------+
| Debian 11 (arm) | PASS |
+------------------+----------------+
| Fedora 37 | PASS |
+------------------+----------------+
| Fedora 38 | PASS |
+------------------+----------------+
| Ubuntu 20.04 | PASS |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
| RHEL8 | PASS |
+------------------+----------------+
| Ubuntu 22.04 | PASS |
+------------------+----------------+
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28599/
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-22 22:24 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 22:24 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-24 10:54 dpdklab
2024-03-24 10:18 dpdklab
2024-03-23 1:41 dpdklab
2024-03-22 23:01 dpdklab
2024-03-22 22:43 dpdklab
2024-03-22 22:34 dpdklab
2024-03-22 22:31 dpdklab
2024-03-22 22:30 dpdklab
2024-03-22 22:28 dpdklab
2024-03-22 22:27 dpdklab
2024-03-22 22:27 dpdklab
2024-03-22 22:24 dpdklab
2024-03-22 22:23 dpdklab
2024-03-22 22:08 dpdklab
2024-03-22 22:07 dpdklab
2024-03-22 22:07 dpdklab
2024-03-22 22:07 dpdklab
2024-03-22 22:06 dpdklab
2024-03-22 22:06 dpdklab
2024-03-22 22:05 dpdklab
2024-03-22 22:05 dpdklab
2024-03-22 22:03 dpdklab
2024-03-22 22:03 dpdklab
2024-03-22 22:03 dpdklab
2024-03-22 22:03 dpdklab
2024-03-22 22:02 dpdklab
2024-03-22 22:01 dpdklab
2024-03-22 22:00 dpdklab
2024-03-22 21:52 dpdklab
2024-03-22 21:51 dpdklab
2024-03-22 21:51 dpdklab
2024-03-22 21:50 dpdklab
2024-03-22 21:50 dpdklab
2024-03-22 21:50 dpdklab
2024-03-22 21:50 dpdklab
2024-03-22 21:50 dpdklab
2024-03-22 21:49 dpdklab
2024-03-22 21:49 dpdklab
2024-03-22 21:46 dpdklab
2024-03-22 21:45 dpdklab
2024-03-22 21:45 dpdklab
2024-03-22 21:45 dpdklab
2024-03-22 21:45 dpdklab
2024-03-22 21:44 dpdklab
2024-03-22 21:44 dpdklab
2024-03-22 21:44 dpdklab
2024-03-22 21:41 dpdklab
2024-03-22 21:32 dpdklab
2024-03-22 21:32 dpdklab
2024-03-22 21:32 dpdklab
2024-03-22 21:31 dpdklab
2024-03-22 21:31 dpdklab
2024-03-22 21:25 dpdklab
2024-03-22 21:19 dpdklab
2024-03-22 21:18 dpdklab
2024-03-22 21:04 dpdklab
2024-03-22 21:04 dpdklab
2024-03-22 21:03 dpdklab
2024-03-22 21:03 dpdklab
2024-03-22 21:02 dpdklab
2024-03-22 20:56 dpdklab
2024-03-22 20:55 dpdklab
2024-03-22 20:50 dpdklab
2024-03-22 20:45 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=65fe0532.170a0220.32fd2.0dabSMTPIN_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).