From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138423-138430 [PATCH] [v4,8/8] crypto/cnxk: update the c
Date: Fri, 15 Mar 2024 01:08:30 -0700 (PDT) [thread overview]
Message-ID: <65f401fe.4a0a0220.f0589.bcc4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240315064511.639-9-vvelumuri@marvell.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138430
_Functional Testing PASS_
Submitter: Vidya Sagar Velumuri <vvelumuri@marvell.com>
Date: Friday, March 15 2024 06:45:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cd218549b686d6be394ef3b171eafa16c038bfe3
138423-138430 --> 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/29570/
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-15 8:08 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240315064511.639-9-vvelumuri@marvell.com>
2024-03-15 6:31 ` |SUCCESS| pw138423-138430 [PATCH v4 8/8] crypto/cnxk: update the context structure of tls qemudev
2024-03-15 6:35 ` qemudev
2024-03-15 6:48 ` |SUCCESS| pw138430 " checkpatch
2024-03-15 7:43 ` 0-day Robot
2024-03-15 8:02 ` |SUCCESS| pw138423-138430 [PATCH] [v4,8/8] crypto/cnxk: update the c dpdklab
2024-03-15 8:04 ` dpdklab
2024-03-15 8:06 ` dpdklab
2024-03-15 8:08 ` dpdklab [this message]
2024-03-15 8:09 ` dpdklab
2024-03-15 8:10 ` dpdklab
2024-03-15 8:13 ` dpdklab
2024-03-15 8:34 ` dpdklab
2024-03-15 8:39 ` dpdklab
2024-03-15 8:40 ` dpdklab
2024-03-15 8:40 ` dpdklab
2024-03-15 8:40 ` dpdklab
2024-03-15 8:40 ` dpdklab
2024-03-15 8:41 ` dpdklab
2024-03-15 8:41 ` dpdklab
2024-03-15 8:41 ` dpdklab
2024-03-15 8:42 ` dpdklab
2024-03-15 8:42 ` dpdklab
2024-03-15 8:43 ` dpdklab
2024-03-15 8:46 ` dpdklab
2024-03-15 8:46 ` dpdklab
2024-03-15 9:16 ` dpdklab
2024-03-15 9:17 ` dpdklab
2024-03-15 9:17 ` dpdklab
2024-03-15 9:17 ` dpdklab
2024-03-15 9:17 ` dpdklab
2024-03-15 9:18 ` dpdklab
2024-03-15 9:18 ` dpdklab
2024-03-15 9:18 ` dpdklab
2024-03-15 9:19 ` dpdklab
2024-03-15 9:19 ` dpdklab
2024-03-15 9:19 ` dpdklab
2024-03-15 9:19 ` dpdklab
2024-03-15 9:19 ` dpdklab
2024-03-15 9:20 ` dpdklab
2024-03-15 9:20 ` dpdklab
2024-03-15 9:20 ` dpdklab
2024-03-15 9:21 ` dpdklab
2024-03-15 9:21 ` dpdklab
2024-03-15 9:21 ` dpdklab
2024-03-15 9:21 ` dpdklab
2024-03-15 9:21 ` dpdklab
2024-03-15 9:21 ` dpdklab
2024-03-15 9:22 ` dpdklab
2024-03-15 9:22 ` dpdklab
2024-03-15 9:22 ` dpdklab
2024-03-15 9:22 ` dpdklab
2024-03-15 9:22 ` dpdklab
2024-03-15 9:22 ` dpdklab
2024-03-15 9:22 ` dpdklab
2024-03-15 9:23 ` dpdklab
2024-03-15 9:23 ` dpdklab
2024-03-15 9:23 ` dpdklab
2024-03-15 9:23 ` dpdklab
2024-03-15 9:23 ` dpdklab
2024-03-15 9:25 ` dpdklab
2024-03-15 9:25 ` dpdklab
2024-03-15 9:27 ` dpdklab
2024-03-15 9:33 ` dpdklab
2024-03-15 9:34 ` dpdklab
2024-03-15 9:35 ` dpdklab
2024-03-15 9:42 ` dpdklab
2024-03-15 9:46 ` dpdklab
2024-03-15 9:53 ` dpdklab
2024-03-15 9:56 ` dpdklab
2024-03-15 9:56 ` dpdklab
2024-03-15 10:09 ` dpdklab
2024-03-15 10:36 ` dpdklab
2024-03-15 10:43 ` dpdklab
2024-03-19 4:26 ` dpdklab
2024-03-19 5:07 ` 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=65f401fe.4a0a0220.f0589.bcc4SMTPIN_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).