From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw126918 [PATCH] [v2] test/crypto: free memory in error and skip paths
Date: Wed, 17 May 2023 06:22:42 -0700 (PDT) [thread overview]
Message-ID: <6464d522.650a0220.daee3.5405SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/126918
_Functional Testing PASS_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Wednesday, May 17 2023 10:55:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a399d7b5a994e335c446d4b15d7622d71dd8848c
126918 --> 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
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/26257/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-05-17 13:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 13:22 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-17 20:05 dpdklab
2023-05-17 20:05 dpdklab
2023-05-17 17:24 dpdklab
2023-05-17 17:18 dpdklab
2023-05-17 15:13 dpdklab
2023-05-17 15:09 dpdklab
2023-05-17 15:04 dpdklab
2023-05-17 15:03 dpdklab
2023-05-17 15:00 dpdklab
2023-05-17 14:58 dpdklab
2023-05-17 14:56 dpdklab
2023-05-17 14:56 dpdklab
2023-05-17 14:52 dpdklab
2023-05-17 14:48 dpdklab
2023-05-17 14:40 dpdklab
2023-05-17 14:19 dpdklab
2023-05-17 14:15 dpdklab
[not found] <20230517105529.405-1-anoobj@marvell.com>
2023-05-17 10:44 ` |SUCCESS| pw126918 [PATCH v2] " qemudev
2023-05-17 10:48 ` qemudev
2023-05-17 10:55 ` checkpatch
2023-05-17 14:00 ` 0-day Robot
2023-05-17 13:51 |SUCCESS| pw126918 [PATCH] [v2] " dpdklab
2023-05-17 13:46 dpdklab
2023-05-17 13:36 dpdklab
2023-05-17 13:34 dpdklab
2023-05-17 13:33 dpdklab
2023-05-17 13:27 dpdklab
2023-05-17 13:27 dpdklab
2023-05-17 13:26 dpdklab
2023-05-17 13:26 dpdklab
2023-05-17 13:22 dpdklab
2023-05-17 13:21 dpdklab
2023-05-17 13:18 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=6464d522.650a0220.daee3.5405SMTPIN_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).