From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134005 [PATCH] crypto/mlx5: fix crypto dev leak
Date: Thu, 09 Nov 2023 02:08:38 -0800 (PST) [thread overview]
Message-ID: <654cafa6.920a0220.c2386.f798SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/134005
_Functional Testing PASS_
Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Thursday, November 09 2023 07:33:17
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:de0ec3c2458e3e2ce53e504c4ba92a36fcc78ef3
134005 --> 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28292/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-09 10:08 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 10:08 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-14 0:05 dpdklab
2023-11-09 19:51 dpdklab
2023-11-09 13:50 dpdklab
2023-11-09 12:57 dpdklab
2023-11-09 12:53 dpdklab
2023-11-09 12:20 dpdklab
2023-11-09 12:13 dpdklab
2023-11-09 12:12 dpdklab
2023-11-09 12:11 dpdklab
2023-11-09 12:10 dpdklab
2023-11-09 12:01 dpdklab
2023-11-09 11:56 dpdklab
2023-11-09 11:56 dpdklab
2023-11-09 11:53 dpdklab
2023-11-09 11:50 dpdklab
2023-11-09 11:42 dpdklab
2023-11-09 11:42 dpdklab
2023-11-09 11:41 dpdklab
2023-11-09 11:35 dpdklab
2023-11-09 11:34 dpdklab
2023-11-09 11:34 dpdklab
2023-11-09 11:33 dpdklab
2023-11-09 11:32 dpdklab
2023-11-09 11:29 dpdklab
2023-11-09 11:28 dpdklab
2023-11-09 11:28 dpdklab
2023-11-09 11:28 dpdklab
2023-11-09 11:27 dpdklab
2023-11-09 11:27 dpdklab
2023-11-09 11:26 dpdklab
2023-11-09 11:26 dpdklab
2023-11-09 11:25 dpdklab
2023-11-09 11:24 dpdklab
2023-11-09 11:23 dpdklab
2023-11-09 11:21 dpdklab
2023-11-09 11:20 dpdklab
2023-11-09 11:19 dpdklab
2023-11-09 11:18 dpdklab
2023-11-09 11:09 dpdklab
2023-11-09 11:09 dpdklab
2023-11-09 10:55 dpdklab
2023-11-09 10:55 dpdklab
2023-11-09 10:09 dpdklab
2023-11-09 10:08 dpdklab
2023-11-09 10:07 dpdklab
2023-11-09 10:06 dpdklab
2023-11-09 10:06 dpdklab
2023-11-09 10:04 dpdklab
2023-11-09 10:02 dpdklab
2023-11-09 10:00 dpdklab
2023-11-09 9:59 dpdklab
[not found] <20231109073317.1311513-1-suanmingm@nvidia.com>
2023-11-09 7:20 ` qemudev
2023-11-09 7:24 ` qemudev
2023-11-09 7:34 ` checkpatch
2023-11-09 8:39 ` 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=654cafa6.920a0220.c2386.f798SMTPIN_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).