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| pw132276-132280 [PATCH] [v2,5/5] cryptodev: add details of
Date: Tue, 03 Oct 2023 07:01:06 -0700 (PDT) [thread overview]
Message-ID: <651c1ea2.170a0220.cff9.24dfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132280
_Testing PASS_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Tuesday, October 03 2023 10:48:54
DPDK git baseline: Repo:dpdk-next-crypto
Branch: master
CommitID:567703b176f24e1734ae3cb4d4c90cc5dd02de4e
132276-132280 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-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
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)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27810/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-03 14:01 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 14:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-03 15:12 dpdklab
2023-10-03 15:07 dpdklab
2023-10-03 15:04 dpdklab
2023-10-03 15:03 dpdklab
2023-10-03 14:55 dpdklab
2023-10-03 14:51 dpdklab
2023-10-03 14:50 dpdklab
2023-10-03 14:38 dpdklab
2023-10-03 14:27 dpdklab
2023-10-03 14:17 dpdklab
2023-10-03 14:15 dpdklab
2023-10-03 14:14 dpdklab
2023-10-03 14:13 dpdklab
2023-10-03 14:11 dpdklab
2023-10-03 14:07 dpdklab
2023-10-03 14:07 dpdklab
2023-10-03 14:03 dpdklab
2023-10-03 14:03 dpdklab
2023-10-03 13:58 dpdklab
2023-10-03 13:53 dpdklab
2023-10-03 13:51 dpdklab
2023-10-03 13:50 dpdklab
2023-10-03 13:48 dpdklab
2023-10-03 13:47 dpdklab
2023-10-03 13:47 dpdklab
2023-10-03 13:41 dpdklab
2023-10-03 13:38 dpdklab
2023-10-03 13:32 dpdklab
2023-10-03 13:25 dpdklab
2023-10-03 13:19 dpdklab
2023-10-03 13:19 dpdklab
2023-10-03 13:13 dpdklab
2023-10-03 13:01 dpdklab
2023-10-03 12:08 dpdklab
2023-10-03 12:00 dpdklab
2023-10-03 11:59 dpdklab
2023-10-03 11:56 dpdklab
2023-10-03 11:55 dpdklab
2023-10-03 11:53 dpdklab
2023-10-03 11:53 dpdklab
2023-10-03 11:51 dpdklab
2023-10-03 11:50 dpdklab
2023-10-03 11:46 dpdklab
2023-10-03 11:43 dpdklab
2023-10-03 11:39 dpdklab
2023-10-03 11:36 dpdklab
2023-10-03 11:36 dpdklab
2023-10-03 11:32 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=651c1ea2.170a0220.cff9.24dfSMTPIN_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).