From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124608 [PATCH] crypto/qat: fix SM3 auth mode
Date: Wed, 1 Mar 2023 22:19:21 +0000 (UTC) [thread overview]
Message-ID: <20230301221921.18A43601F7@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/124608
_Functional Testing PASS_
Submitter: Ciara Power <ciara.power@intel.com>
Date: Wednesday, March 01 2023 13:59:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124608 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25575/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-01 22:19 UTC|newest]
Thread overview: 105+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 22:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-03 0:30 dpdklab
2023-03-03 0:29 dpdklab
2023-03-03 0:21 dpdklab
2023-03-03 0:18 dpdklab
2023-03-03 0:11 dpdklab
2023-03-03 0:09 dpdklab
2023-03-03 0:07 dpdklab
2023-03-03 0:05 dpdklab
2023-03-02 23:55 dpdklab
2023-03-02 23:53 dpdklab
2023-03-02 23:51 dpdklab
2023-03-02 23:49 dpdklab
2023-03-02 23:48 dpdklab
2023-03-02 23:39 dpdklab
2023-03-02 22:49 dpdklab
2023-03-02 22:49 dpdklab
2023-03-02 22:45 dpdklab
2023-03-02 22:40 dpdklab
2023-03-02 22:37 dpdklab
2023-03-02 22:32 dpdklab
2023-03-02 22:24 dpdklab
2023-03-02 22:23 dpdklab
2023-03-02 22:21 dpdklab
2023-03-02 22:18 dpdklab
2023-03-02 22:14 dpdklab
2023-03-02 22:13 dpdklab
2023-03-02 22:08 dpdklab
2023-03-02 22:03 dpdklab
2023-03-02 21:58 dpdklab
2023-03-02 21:58 dpdklab
2023-03-02 21:53 dpdklab
2023-03-02 21:49 dpdklab
2023-03-02 21:38 dpdklab
2023-03-02 21:35 dpdklab
2023-03-02 21:28 dpdklab
2023-03-02 21:27 dpdklab
2023-03-02 21:25 dpdklab
2023-03-02 21:22 dpdklab
2023-03-02 21:20 dpdklab
2023-03-02 21:13 dpdklab
2023-03-02 21:04 dpdklab
2023-03-02 21:04 dpdklab
2023-03-02 21:03 dpdklab
2023-03-02 20:52 dpdklab
2023-03-02 20:22 dpdklab
2023-03-02 20:20 dpdklab
2023-03-02 20:16 dpdklab
2023-03-02 20:15 dpdklab
2023-03-02 20:14 dpdklab
2023-03-02 20:12 dpdklab
2023-03-02 20:06 dpdklab
2023-03-02 20:01 dpdklab
2023-03-02 19:52 dpdklab
2023-03-02 19:51 dpdklab
2023-03-02 19:48 dpdklab
2023-03-02 19:46 dpdklab
2023-03-02 7:37 dpdklab
2023-03-02 5:52 dpdklab
2023-03-02 4:53 dpdklab
2023-03-02 4:45 dpdklab
2023-03-02 4:44 dpdklab
2023-03-02 3:50 dpdklab
2023-03-02 3:36 dpdklab
2023-03-02 3:02 dpdklab
2023-03-01 23:24 dpdklab
2023-03-01 23:13 dpdklab
2023-03-01 23:13 dpdklab
2023-03-01 23:00 dpdklab
2023-03-01 22:15 dpdklab
2023-03-01 22:07 dpdklab
2023-03-01 22:04 dpdklab
2023-03-01 22:00 dpdklab
2023-03-01 21:49 dpdklab
2023-03-01 21:48 dpdklab
2023-03-01 21:46 dpdklab
2023-03-01 21:21 dpdklab
2023-03-01 21:10 dpdklab
2023-03-01 21:09 dpdklab
2023-03-01 21:07 dpdklab
2023-03-01 21:03 dpdklab
2023-03-01 20:56 dpdklab
2023-03-01 20:49 dpdklab
2023-03-01 20:40 dpdklab
2023-03-01 20:39 dpdklab
2023-03-01 20:39 dpdklab
2023-03-01 20:39 dpdklab
2023-03-01 20:33 dpdklab
2023-03-01 20:32 dpdklab
2023-03-01 20:29 dpdklab
2023-03-01 20:28 dpdklab
2023-03-01 20:26 dpdklab
2023-03-01 20:24 dpdklab
2023-03-01 20:23 dpdklab
2023-03-01 20:20 dpdklab
2023-03-01 20:18 dpdklab
2023-03-01 20:16 dpdklab
2023-03-01 20:14 dpdklab
2023-03-01 20:13 dpdklab
2023-03-01 20:08 dpdklab
2023-03-01 20:07 dpdklab
[not found] <20230301135915.2184760-1-ciara.power@intel.com>
2023-03-01 13:52 ` qemudev
2023-03-01 13:56 ` qemudev
2023-03-01 14:00 ` checkpatch
2023-03-01 15:59 ` 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=20230301221921.18A43601F7@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).