From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138354-138365 [PATCH] [12/12] crypto/cnxk: remove the re
Date: Thu, 14 Mar 2024 08:01:00 -0700 (PDT) [thread overview]
Message-ID: <65f3112c.170a0220.918a5.0e36SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240314083844.3319506-13-vvelumuri@marvell.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138365
_Functional Testing PASS_
Submitter: Vidya Sagar Velumuri <vvelumuri@marvell.com>
Date: Thursday, March 14 2024 08:38:44
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cd218549b686d6be394ef3b171eafa16c038bfe3
138354-138365 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-82
Compiler: gcc 11.4.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/1
Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29544/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-14 15:01 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240314083844.3319506-13-vvelumuri@marvell.com>
2024-03-14 8:18 ` |SUCCESS| pw138354-138365 [PATCH 12/12] crypto/cnxk: remove the response len handling for tls qemudev
2024-03-14 8:23 ` qemudev
2024-03-14 8:41 ` |SUCCESS| pw138365 " checkpatch
2024-03-14 9:11 ` |SUCCESS| pw138354-138365 [PATCH] [12/12] crypto/cnxk: remove the re dpdklab
2024-03-14 9:12 ` dpdklab
2024-03-14 9:13 ` dpdklab
2024-03-14 9:13 ` dpdklab
2024-03-14 9:14 ` dpdklab
2024-03-14 9:15 ` dpdklab
2024-03-14 9:15 ` dpdklab
2024-03-14 9:15 ` dpdklab
2024-03-14 9:16 ` dpdklab
2024-03-14 9:16 ` dpdklab
2024-03-14 9:16 ` dpdklab
2024-03-14 9:17 ` dpdklab
2024-03-14 9:18 ` dpdklab
2024-03-14 9:18 ` dpdklab
2024-03-14 9:18 ` dpdklab
2024-03-14 9:19 ` dpdklab
2024-03-14 9:19 ` dpdklab
2024-03-14 9:19 ` dpdklab
2024-03-14 9:20 ` dpdklab
2024-03-14 9:20 ` dpdklab
2024-03-14 9:21 ` dpdklab
2024-03-14 9:22 ` dpdklab
2024-03-14 9:25 ` dpdklab
2024-03-14 9:26 ` dpdklab
2024-03-14 9:26 ` dpdklab
2024-03-14 9:26 ` dpdklab
2024-03-14 9:26 ` dpdklab
2024-03-14 9:26 ` dpdklab
2024-03-14 9:26 ` dpdklab
2024-03-14 9:27 ` dpdklab
2024-03-14 9:27 ` |FAILURE| " dpdklab
2024-03-14 9:27 ` |SUCCESS| " dpdklab
2024-03-14 9:27 ` dpdklab
2024-03-14 9:27 ` dpdklab
2024-03-14 9:28 ` dpdklab
2024-03-14 9:28 ` dpdklab
2024-03-14 9:28 ` dpdklab
2024-03-14 9:28 ` dpdklab
2024-03-14 9:28 ` dpdklab
2024-03-14 9:28 ` dpdklab
2024-03-14 9:30 ` dpdklab
2024-03-14 9:31 ` dpdklab
2024-03-14 9:31 ` dpdklab
2024-03-14 9:31 ` dpdklab
2024-03-14 9:31 ` dpdklab
2024-03-14 9:32 ` dpdklab
2024-03-14 9:32 ` dpdklab
2024-03-14 9:32 ` dpdklab
2024-03-14 9:32 ` dpdklab
2024-03-14 9:33 ` dpdklab
2024-03-14 9:33 ` dpdklab
2024-03-14 9:33 ` dpdklab
2024-03-14 9:33 ` dpdklab
2024-03-14 9:34 ` dpdklab
2024-03-14 9:34 ` dpdklab
2024-03-14 9:34 ` dpdklab
2024-03-14 9:34 ` dpdklab
2024-03-14 9:35 ` dpdklab
2024-03-14 9:35 ` dpdklab
2024-03-14 9:36 ` dpdklab
2024-03-14 9:36 ` dpdklab
2024-03-14 9:36 ` dpdklab
2024-03-14 9:37 ` dpdklab
2024-03-14 9:43 ` |SUCCESS| pw138365 [PATCH 12/12] crypto/cnxk: remove the response len handling for tls 0-day Robot
2024-03-14 9:53 ` |SUCCESS| pw138354-138365 [PATCH] [12/12] crypto/cnxk: remove the re dpdklab
2024-03-14 9:53 ` dpdklab
2024-03-14 9:54 ` dpdklab
2024-03-14 9:56 ` dpdklab
2024-03-14 9:57 ` dpdklab
2024-03-14 9:59 ` dpdklab
2024-03-14 10:01 ` dpdklab
2024-03-14 10:04 ` dpdklab
2024-03-14 10:40 ` dpdklab
2024-03-14 10:51 ` dpdklab
2024-03-14 15:01 ` dpdklab [this message]
2024-03-14 15:05 ` dpdklab
2024-03-14 15:07 ` dpdklab
2024-03-14 15:10 ` dpdklab
2024-03-14 15:11 ` dpdklab
2024-03-14 15:11 ` dpdklab
2024-03-14 15:13 ` dpdklab
2024-03-14 15:14 ` dpdklab
2024-03-14 15:15 ` dpdklab
2024-03-14 15:23 ` dpdklab
2024-03-14 15:23 ` dpdklab
2024-03-14 15:26 ` dpdklab
2024-03-18 0:01 ` dpdklab
2024-03-18 0:37 ` dpdklab
2024-03-18 9:14 ` dpdklab
2024-03-18 9:45 ` 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=65f3112c.170a0220.918a5.0e36SMTPIN_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).