From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131177-131178 [PATCH] [v5,2/2] test/crypto: fix IV in so
Date: Tue, 05 Sep 2023 23:08:18 -0700 (PDT) [thread overview]
Message-ID: <64f81752.050a0220.307f3.949cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131178
_Testing PASS_
Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Tuesday, September 05 2023 16:15:07
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e92ba1426914db1d224dd5e9a1743657681b8814
131177-131178 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27529/
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-06 6:08 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 6:08 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-06 9:04 dpdklab
2023-09-06 9:02 dpdklab
2023-09-06 8:47 dpdklab
2023-09-06 8:40 dpdklab
2023-09-06 8:35 dpdklab
2023-09-06 7:27 dpdklab
2023-09-06 7:07 dpdklab
2023-09-06 7:04 dpdklab
2023-09-06 7:02 dpdklab
2023-09-06 7:00 dpdklab
2023-09-06 6:56 dpdklab
2023-09-06 6:52 dpdklab
2023-09-06 6:48 dpdklab
2023-09-06 6:46 dpdklab
2023-09-06 6:45 dpdklab
2023-09-06 6:37 dpdklab
2023-09-06 6:36 dpdklab
2023-09-06 6:36 dpdklab
2023-09-06 6:33 dpdklab
2023-09-06 6:33 dpdklab
2023-09-06 6:33 dpdklab
2023-09-06 6:29 dpdklab
2023-09-06 6:29 dpdklab
2023-09-06 6:26 dpdklab
2023-09-06 6:25 dpdklab
2023-09-06 6:21 dpdklab
2023-09-06 6:17 dpdklab
2023-09-06 6:14 dpdklab
2023-09-06 6:10 dpdklab
2023-09-06 6:09 dpdklab
2023-09-06 6:06 dpdklab
2023-09-06 6:03 dpdklab
2023-09-06 6:00 dpdklab
2023-09-06 5:28 dpdklab
2023-09-06 5:28 dpdklab
2023-09-06 5:28 dpdklab
2023-09-06 5:27 dpdklab
2023-09-06 5:26 dpdklab
2023-09-06 5:26 dpdklab
2023-09-06 5:24 dpdklab
2023-09-06 5:08 dpdklab
2023-09-06 5:05 dpdklab
2023-09-06 5:02 dpdklab
2023-09-06 4:52 dpdklab
2023-09-06 4:51 dpdklab
2023-09-06 4:50 dpdklab
2023-09-06 4:48 dpdklab
2023-09-06 4:41 dpdklab
2023-09-06 4:39 dpdklab
2023-09-06 4:35 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=64f81752.050a0220.307f3.949cSMTPIN_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).