From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135337-135340 [PATCH] [4/4] crypto/qat: disable asym and
Date: Tue, 19 Dec 2023 10:55:57 -0800 (PST) [thread overview]
Message-ID: <6581e73d.050a0220.87893.bc2cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/135340
_Functional Testing PASS_
Submitter: Ciara Power <ciara.power@intel.com>
Date: Tuesday, December 19 2023 15:51:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135337-135340 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28685/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-19 18:55 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 18:55 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-19 19:17 dpdklab
2023-12-19 18:47 dpdklab
2023-12-19 18:45 dpdklab
2023-12-19 18:39 dpdklab
2023-12-19 18:36 dpdklab
2023-12-19 18:30 dpdklab
2023-12-19 18:12 dpdklab
2023-12-19 18:08 dpdklab
2023-12-19 18:06 dpdklab
2023-12-19 18:05 dpdklab
2023-12-19 18:05 dpdklab
2023-12-19 18:02 dpdklab
2023-12-19 18:02 dpdklab
2023-12-19 18:01 dpdklab
2023-12-19 18:00 dpdklab
2023-12-19 17:58 dpdklab
2023-12-19 17:58 dpdklab
2023-12-19 17:57 dpdklab
2023-12-19 17:57 dpdklab
2023-12-19 17:56 dpdklab
2023-12-19 17:55 dpdklab
2023-12-19 17:54 dpdklab
2023-12-19 17:54 dpdklab
2023-12-19 17:53 dpdklab
2023-12-19 17:53 dpdklab
2023-12-19 17:53 dpdklab
2023-12-19 17:53 dpdklab
2023-12-19 17:52 dpdklab
2023-12-19 17:52 dpdklab
2023-12-19 17:51 dpdklab
2023-12-19 17:51 dpdklab
2023-12-19 17:50 dpdklab
2023-12-19 17:50 dpdklab
2023-12-19 17:50 dpdklab
2023-12-19 17:49 dpdklab
2023-12-19 17:49 dpdklab
2023-12-19 17:48 dpdklab
2023-12-19 17:48 dpdklab
2023-12-19 17:48 dpdklab
2023-12-19 17:47 dpdklab
2023-12-19 17:47 dpdklab
2023-12-19 17:47 dpdklab
2023-12-19 17:47 dpdklab
2023-12-19 17:47 dpdklab
2023-12-19 17:46 dpdklab
2023-12-19 17:46 dpdklab
2023-12-19 17:46 dpdklab
2023-12-19 17:46 dpdklab
2023-12-19 17:46 dpdklab
2023-12-19 17:45 dpdklab
2023-12-19 17:45 dpdklab
2023-12-19 17:45 dpdklab
2023-12-19 17:45 dpdklab
2023-12-19 17:44 dpdklab
2023-12-19 17:44 dpdklab
2023-12-19 17:44 dpdklab
2023-12-19 17:43 dpdklab
2023-12-19 17:43 dpdklab
2023-12-19 17:43 dpdklab
2023-12-19 17:43 dpdklab
2023-12-19 17:43 dpdklab
2023-12-19 17:43 dpdklab
2023-12-19 17:42 dpdklab
2023-12-19 17:42 dpdklab
2023-12-19 17:42 dpdklab
2023-12-19 17:41 dpdklab
2023-12-19 17:41 dpdklab
2023-12-19 17:40 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=6581e73d.050a0220.87893.bc2cSMTPIN_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).