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] 6ca8a873f715e19550fc7dd43ce94af54158a725
Date: Wed, 26 Jun 2024 20:56:10 -0700 (PDT) [thread overview]
Message-ID: <667ce2da.170a0220.122d9.bad4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-crypto
6ca8a873f715e19550fc7dd43ce94af54158a725 --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
| CentOS Stream 9 | PASS |
+-----------------+----------------+
| Debian Bullseye | PASS |
+-----------------+----------------+
| Fedora 37 | PASS |
+-----------------+----------------+
| Debian 12 | PASS |
+-----------------+----------------+
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 Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29605/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-06-27 3:56 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 3:56 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-28 11:21 dpdklab
2024-06-27 20:43 dpdklab
2024-06-27 19:39 dpdklab
2024-06-27 5:57 dpdklab
2024-06-27 5:56 dpdklab
2024-06-27 5:51 dpdklab
2024-06-27 5:50 dpdklab
2024-06-27 5:48 dpdklab
2024-06-27 5:44 dpdklab
2024-06-27 5:43 dpdklab
2024-06-27 5:33 dpdklab
2024-06-27 5:31 dpdklab
2024-06-27 5:23 dpdklab
2024-06-27 5:22 dpdklab
2024-06-27 5:21 dpdklab
2024-06-27 5:14 dpdklab
2024-06-27 5:14 dpdklab
2024-06-27 5:13 dpdklab
2024-06-27 5:13 dpdklab
2024-06-27 5:12 dpdklab
2024-06-27 5:11 dpdklab
2024-06-27 5:10 dpdklab
2024-06-27 5:07 dpdklab
2024-06-27 5:05 dpdklab
2024-06-27 5:02 dpdklab
2024-06-27 4:56 dpdklab
2024-06-27 4:52 dpdklab
2024-06-27 4:50 dpdklab
2024-06-27 4:50 dpdklab
2024-06-27 4:45 dpdklab
2024-06-27 4:45 dpdklab
2024-06-27 4:30 dpdklab
2024-06-27 4:21 dpdklab
2024-06-27 4:20 dpdklab
2024-06-27 4:17 dpdklab
2024-06-27 4:17 dpdklab
2024-06-27 4:15 dpdklab
2024-06-27 4:14 dpdklab
2024-06-27 4:09 dpdklab
2024-06-27 4:09 dpdklab
2024-06-27 4:04 dpdklab
2024-06-27 4:02 dpdklab
2024-06-27 3:58 dpdklab
2024-06-27 3:56 dpdklab
2024-06-27 3:55 dpdklab
2024-06-27 3:52 dpdklab
2024-06-27 3:49 dpdklab
2024-06-27 3:48 dpdklab
2024-06-27 3:44 dpdklab
2024-06-27 3:37 dpdklab
2024-06-27 3:35 dpdklab
2024-06-27 3:33 dpdklab
2024-06-27 3:28 dpdklab
2024-06-27 3:26 dpdklab
2024-06-27 3:24 dpdklab
2024-06-27 3:21 dpdklab
2024-06-27 3:17 dpdklab
2024-06-27 3:17 dpdklab
2024-06-27 3:15 dpdklab
2024-06-27 3:12 dpdklab
2024-06-27 3:09 dpdklab
2024-06-27 2:49 dpdklab
2024-06-27 2:18 dpdklab
2024-06-27 2:13 dpdklab
2024-06-27 1:53 dpdklab
2024-06-27 1:48 dpdklab
2024-06-27 1:44 dpdklab
2024-06-27 1:21 dpdklab
2024-06-27 0:59 dpdklab
2024-06-27 0:56 dpdklab
2024-06-27 0:55 dpdklab
2024-06-27 0:49 dpdklab
2024-06-26 23:56 dpdklab
2024-06-26 23:30 dpdklab
2024-06-26 23:23 dpdklab
2024-06-26 23:07 dpdklab
2024-06-26 22:11 dpdklab
2024-06-26 22:05 dpdklab
2024-06-26 21:58 dpdklab
2024-06-26 21:57 dpdklab
2024-06-26 21:51 dpdklab
2024-06-26 21:44 dpdklab
2024-06-26 21:43 dpdklab
2024-06-26 21:08 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=667ce2da.170a0220.122d9.bad4SMTPIN_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).