From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129298 [PATCH] crypto/qat: fix legacy sm4 ecb capability
Date: Mon, 10 Jul 2023 10:52:52 -0700 (PDT) [thread overview]
Message-ID: <64ac4574.050a0220.809ed.0524SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-aarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129298
_Testing PASS_
Submitter: Power, Ciara <ciara.power@intel.com>
Date: Wednesday, July 05 2023 13:23:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a64a4564705d18d20d20cfa16c79e795b7bf0f1e
129298 --> testing pass
Test environment and result as below:
+-----------------------------+------------------------------+---------------------------+--------------+----------------+
| Environment | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | lpm_autotest | dpdk_unit_test |
+=============================+==============================+===========================+==============+================+
| Debian 11 | PASS | PASS | SKIPPED | SKIPPED |
+-----------------------------+------------------------------+---------------------------+--------------+----------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | SKIPPED | PASS | SKIPPED |
+-----------------------------+------------------------------+---------------------------+--------------+----------------+
| (32-bit) ARM Ubuntu 20.04.4 | SKIPPED | SKIPPED | SKIPPED | PASS |
+-----------------------------+------------------------------+---------------------------+--------------+----------------+
Debian 11
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
(32-bit) ARM Ubuntu 20.04.4
Kernel: 5.4.0-148-generic aarch64
Compiler: gcc 9.4
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26977/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-10 17:52 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 17:52 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-12 22:42 dpdklab
2023-07-12 22:41 dpdklab
2023-07-10 18:09 dpdklab
2023-07-08 20:33 dpdklab
2023-07-08 13:32 dpdklab
2023-07-07 21:00 dpdklab
2023-07-07 0:19 dpdklab
2023-07-07 0:10 dpdklab
2023-07-07 0:04 dpdklab
2023-07-06 23:48 dpdklab
2023-07-06 23:43 dpdklab
2023-07-05 21:55 dpdklab
2023-07-05 20:24 dpdklab
2023-07-05 20:05 dpdklab
2023-07-05 20:02 dpdklab
2023-07-05 19:13 dpdklab
2023-07-05 19:10 dpdklab
2023-07-05 19:09 dpdklab
2023-07-05 19:08 dpdklab
2023-07-05 19:01 dpdklab
2023-07-05 18:52 dpdklab
2023-07-05 18:34 dpdklab
2023-07-05 18:34 dpdklab
2023-07-05 18:33 dpdklab
2023-07-05 18:30 dpdklab
2023-07-05 18:30 dpdklab
2023-07-05 18:30 dpdklab
2023-07-05 18:29 dpdklab
2023-07-05 17:54 dpdklab
2023-07-05 17:32 dpdklab
2023-07-05 17:31 dpdklab
2023-07-05 17:30 dpdklab
2023-07-05 17:30 dpdklab
2023-07-05 17:19 dpdklab
[not found] <20230705132311.1146176-1-ciara.power@intel.com>
2023-07-05 13:16 ` qemudev
2023-07-05 13:21 ` qemudev
2023-07-05 13:24 ` checkpatch
2023-07-05 14:19 ` 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=64ac4574.050a0220.809ed.0524SMTPIN_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).