From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131370 [PATCH] [v2] cryptodev: add missing doc
Date: Tue, 12 Sep 2023 15:01:21 -0700 (PDT) [thread overview]
Message-ID: <6500dfb1.5d0a0220.90fd4.6b92SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131370
_Testing PASS_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Tuesday, September 12 2023 10:42:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e92ba1426914db1d224dd5e9a1743657681b8814
131370 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Debian Bullseye | 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
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
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27584/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-12 22:01 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 22:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-12 22:49 dpdklab
2023-09-12 22:48 dpdklab
2023-09-12 22:24 dpdklab
2023-09-12 22:23 dpdklab
2023-09-12 22:21 dpdklab
2023-09-12 22:20 dpdklab
2023-09-12 22:20 dpdklab
2023-09-12 22:04 dpdklab
2023-09-12 22:02 dpdklab
2023-09-12 22:01 dpdklab
2023-09-12 22:01 dpdklab
2023-09-12 22:01 dpdklab
2023-09-12 22:01 dpdklab
2023-09-12 21:59 dpdklab
2023-09-12 21:57 dpdklab
2023-09-12 21:55 dpdklab
2023-09-12 21:54 dpdklab
2023-09-12 21:53 dpdklab
2023-09-12 21:52 dpdklab
2023-09-12 21:46 dpdklab
2023-09-12 21:46 dpdklab
2023-09-12 21:44 dpdklab
2023-09-12 21:42 dpdklab
2023-09-12 21:41 dpdklab
2023-09-12 21:41 dpdklab
2023-09-12 21:40 dpdklab
2023-09-12 21:39 dpdklab
2023-09-12 21:39 dpdklab
2023-09-12 21:39 dpdklab
2023-09-12 21:39 dpdklab
2023-09-12 21:39 dpdklab
2023-09-12 21:39 dpdklab
2023-09-12 21:38 dpdklab
2023-09-12 21:36 dpdklab
2023-09-12 21:36 dpdklab
2023-09-12 21:34 dpdklab
2023-09-12 21:34 dpdklab
2023-09-12 21:33 dpdklab
2023-09-12 21:27 dpdklab
2023-09-12 21:27 dpdklab
2023-09-12 21:27 dpdklab
2023-09-12 21:26 dpdklab
2023-09-12 21:26 dpdklab
2023-09-12 21:26 dpdklab
2023-09-12 21:22 dpdklab
[not found] <20230912104214.204-1-anoobj@marvell.com>
2023-09-12 10:36 ` |SUCCESS| pw131370 [PATCH v2] " qemudev
2023-09-12 10:40 ` qemudev
2023-09-12 10:43 ` checkpatch
2023-09-12 11:39 ` 0-day Robot
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=6500dfb1.5d0a0220.90fd4.6b92SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).