automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw155981 [PATCH] app/crypto-perf: add ECDSA P384 support
Date: Mon, 18 Aug 2025 23:34:31 -0700 (PDT)	[thread overview]
Message-ID: <68a41af7.d40a0220.2ce92.eb80SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250819050850.1650503-1-rchiluka@marvell.com>

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/155981

_Functional Testing PASS_

Submitter: Rupesh Chiluka <rchiluka@marvell.com>
Date: Tuesday, August 19 2025 05:08:50 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:390cb3d4ea2f9139e18c7541ec68d269bfe3dc37

155981 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#240845

Test environment and result as below:

Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
NIC: Intel Corporation 4xxx Series QAT 0 Mbps

Aggregate Results by Test Suite
+----------------------------+--------+
|         Test Suite         | Result |
+============================+========+
| crypto_perf_cryptodev_perf |  PASS  |
+----------------------------+--------+


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33901/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2025-08-19  6:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250819050850.1650503-1-rchiluka@marvell.com>
2025-08-19  4:59 ` qemudev
2025-08-19  5:04 ` qemudev
2025-08-19  5:07 ` checkpatch
2025-08-19  6:09 ` 0-day Robot
2025-08-19  6:12 ` dpdklab
2025-08-19  6:34 ` dpdklab [this message]
2025-08-19  6:44 ` |PENDING| " dpdklab
2025-08-19  6:47 ` |SUCCESS| " dpdklab
2025-08-19  6:53 ` dpdklab
2025-08-19  7:02 ` |PENDING| " dpdklab
2025-08-19  7:02 ` dpdklab
2025-08-19  7:05 ` dpdklab
2025-08-19  7:19 ` |SUCCESS| " dpdklab
2025-08-19  7:42 ` dpdklab
2025-08-19  8:00 ` dpdklab
2025-08-19  8:18 ` dpdklab
2025-08-19  8:22 ` dpdklab
2025-08-19  8:33 ` dpdklab
2025-08-19  8:46 ` dpdklab
2025-08-19 15:12 ` dpdklab
2025-08-19 16:48 ` dpdklab
2025-08-19 16:56 ` dpdklab
2025-08-19 16:56 ` dpdklab
2025-08-19 16:57 ` dpdklab
2025-08-19 17:43 ` dpdklab
2025-08-19 17:51 ` dpdklab
2025-08-19 18:01 ` dpdklab
2025-08-19 18:05 ` 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=68a41af7.d40a0220.2ce92.eb80SMTPIN_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).