From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130588 [PATCH] [v2] crypto/ipsec_mb: add digest encrypte
Date: Tue, 22 Aug 2023 18:06:12 -0700 (PDT) [thread overview]
Message-ID: <64e55b84.c80a0220.37a7a.b94fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130588
_Testing PASS_
Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Monday, August 21 2023 14:42:34
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:971d2b57972919527e27ed683032a71864a2eb56
130588 --> testing pass
Test environment and result as below:
+--------------------------+---------------------------+------------------------------+----------------+
| Environment | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | dpdk_unit_test |
+==========================+===========================+==============================+================+
| Debian 11 (arm) | PASS | PASS | SKIPPED |
+--------------------------+---------------------------+------------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+---------------------------+------------------------------+----------------+
| Fedora 38 (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+---------------------------+------------------------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+---------------------------+------------------------------+----------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27400/
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-23 1:06 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 1:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-23 15:49 dpdklab
2023-08-23 15:32 dpdklab
2023-08-23 15:27 dpdklab
2023-08-23 15:23 dpdklab
2023-08-23 15:18 dpdklab
2023-08-23 8:16 dpdklab
2023-08-23 3:51 dpdklab
2023-08-23 2:21 dpdklab
2023-08-23 2:03 dpdklab
2023-08-23 1:52 dpdklab
2023-08-23 1:52 dpdklab
2023-08-23 1:52 dpdklab
2023-08-23 1:50 dpdklab
2023-08-23 1:50 dpdklab
2023-08-23 1:49 dpdklab
2023-08-23 1:48 dpdklab
2023-08-23 1:47 dpdklab
2023-08-23 1:45 dpdklab
2023-08-23 1:43 dpdklab
2023-08-23 1:41 dpdklab
2023-08-23 1:40 dpdklab
2023-08-23 1:20 dpdklab
2023-08-23 1:17 dpdklab
2023-08-23 1:12 dpdklab
2023-08-23 1:12 dpdklab
2023-08-23 1:11 dpdklab
2023-08-23 1:11 dpdklab
2023-08-23 1:09 dpdklab
2023-08-23 1:04 dpdklab
2023-08-23 0:57 dpdklab
2023-08-23 0:57 dpdklab
2023-08-23 0:56 dpdklab
2023-08-23 0:46 dpdklab
2023-08-23 0:42 dpdklab
2023-08-23 0:37 dpdklab
2023-08-23 0:37 dpdklab
2023-08-23 0:37 dpdklab
2023-08-23 0:36 dpdklab
2023-08-23 0:36 dpdklab
2023-08-23 0:36 dpdklab
2023-08-23 0:36 dpdklab
2023-08-23 0:35 dpdklab
2023-08-23 0:35 dpdklab
2023-08-23 0:35 dpdklab
2023-08-23 0:35 dpdklab
2023-08-23 0:33 dpdklab
2023-08-23 0:33 dpdklab
2023-08-23 0:33 dpdklab
2023-08-23 0:33 dpdklab
2023-08-23 0:33 dpdklab
2023-08-23 0:15 dpdklab
2023-08-23 0:10 dpdklab
2023-08-23 0:08 dpdklab
2023-08-22 23:03 dpdklab
2023-08-22 22:43 dpdklab
2023-08-22 22:42 dpdklab
2023-08-22 22:37 dpdklab
2023-08-22 22:01 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=64e55b84.c80a0220.37a7a.b94fSMTPIN_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).