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] 197bb4582c43df3c40db97a0da463afea5e74951
Date: Wed, 13 Mar 2024 13:12:59 -0700 (PDT) [thread overview]
Message-ID: <65f208cb.170a0220.9d20c.0032SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-crypto
197bb4582c43df3c40db97a0da463afea5e74951 --> 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 (arm) | PASS |
+-----------------+----------------+
| Fedora 38 | PASS |
+-----------------+----------------+
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
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28471/
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-13 20:13 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 20:12 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-17 11:35 dpdklab
2024-03-17 10:59 dpdklab
2024-03-13 21:26 dpdklab
2024-03-13 21:09 dpdklab
2024-03-13 20:33 dpdklab
2024-03-13 20:32 dpdklab
2024-03-13 20:30 dpdklab
2024-03-13 20:27 dpdklab
2024-03-13 20:26 dpdklab
2024-03-13 20:26 dpdklab
2024-03-13 20:26 dpdklab
2024-03-13 20:23 dpdklab
2024-03-13 20:22 dpdklab
2024-03-13 20:22 dpdklab
2024-03-13 20:22 dpdklab
2024-03-13 20:21 dpdklab
2024-03-13 20:21 dpdklab
2024-03-13 20:20 dpdklab
2024-03-13 20:19 dpdklab
2024-03-13 20:19 dpdklab
2024-03-13 20:18 dpdklab
2024-03-13 20:18 dpdklab
2024-03-13 20:17 dpdklab
2024-03-13 20:17 dpdklab
2024-03-13 20:16 dpdklab
2024-03-13 20:16 dpdklab
2024-03-13 20:16 dpdklab
2024-03-13 20:16 dpdklab
2024-03-13 20:16 dpdklab
2024-03-13 20:15 dpdklab
2024-03-13 20:15 dpdklab
2024-03-13 20:15 dpdklab
2024-03-13 20:15 dpdklab
2024-03-13 20:15 dpdklab
2024-03-13 20:14 dpdklab
2024-03-13 20:14 dpdklab
2024-03-13 20:14 dpdklab
2024-03-13 20:14 dpdklab
2024-03-13 20:14 dpdklab
2024-03-13 20:14 dpdklab
2024-03-13 20:14 dpdklab
2024-03-13 20:14 dpdklab
2024-03-13 20:13 dpdklab
2024-03-13 20:12 dpdklab
2024-03-13 20:12 dpdklab
2024-03-13 20:12 dpdklab
2024-03-13 20:12 dpdklab
2024-03-13 20:11 dpdklab
2024-03-13 20:11 dpdklab
2024-03-13 20:11 dpdklab
2024-03-13 20:11 dpdklab
2024-03-13 20:10 dpdklab
2024-03-13 20:10 dpdklab
2024-03-13 20:10 dpdklab
2024-03-13 20:09 dpdklab
2024-03-13 20:09 dpdklab
2024-03-13 20:09 dpdklab
2024-03-13 20:09 dpdklab
2024-03-13 20: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=65f208cb.170a0220.9d20c.0032SMTPIN_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).