From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130747 [PATCH] [v3] crypto/ipsec_mb: add digest encrypte
Date: Fri, 25 Aug 2023 04:32:48 -0700 (PDT) [thread overview]
Message-ID: <64e89160.020a0220.8fa8f.30bcSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130747
_Testing PASS_
Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Friday, August 25 2023 08:41:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:934c0ccbfe881d861d749a9f8fb146d5f134c04c
130747 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Fedora 38 | 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
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27442/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-25 11:32 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 11:32 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-25 18:44 dpdklab
2023-08-25 18:31 dpdklab
2023-08-25 12:49 dpdklab
2023-08-25 12:45 dpdklab
2023-08-25 12:43 dpdklab
2023-08-25 12:38 dpdklab
2023-08-25 12:35 dpdklab
2023-08-25 12:16 dpdklab
2023-08-25 11:52 dpdklab
2023-08-25 11:49 dpdklab
2023-08-25 11:47 dpdklab
2023-08-25 11:46 dpdklab
2023-08-25 11:45 dpdklab
2023-08-25 11:44 dpdklab
2023-08-25 11:40 dpdklab
2023-08-25 11:35 dpdklab
2023-08-25 11:35 dpdklab
2023-08-25 11:32 dpdklab
2023-08-25 11:32 dpdklab
2023-08-25 11:28 dpdklab
2023-08-25 11:23 dpdklab
2023-08-25 11:21 dpdklab
2023-08-25 11:21 dpdklab
2023-08-25 11:21 dpdklab
2023-08-25 11:18 dpdklab
2023-08-25 11:17 dpdklab
2023-08-25 11:17 dpdklab
2023-08-25 11:17 dpdklab
2023-08-25 11:16 dpdklab
2023-08-25 11:14 dpdklab
2023-08-25 11:13 dpdklab
2023-08-25 11:13 dpdklab
2023-08-25 11:12 dpdklab
2023-08-25 11:12 dpdklab
2023-08-25 11:11 dpdklab
2023-08-25 11:10 dpdklab
2023-08-25 11:07 dpdklab
2023-08-25 11:07 dpdklab
2023-08-25 11:06 dpdklab
2023-08-25 11:05 dpdklab
2023-08-25 11:02 dpdklab
2023-08-25 11:01 dpdklab
2023-08-25 11:01 dpdklab
2023-08-25 10:58 dpdklab
2023-08-25 10:58 dpdklab
2023-08-25 10:57 dpdklab
2023-08-25 10:57 dpdklab
2023-08-25 10:56 dpdklab
2023-08-25 10:56 dpdklab
2023-08-25 10:55 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=64e89160.020a0220.8fa8f.30bcSMTPIN_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).