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, Akhil Goyal <gakhil@marvell.com>,
	Rupesh Chiluka <rchiluka@marvell.com>
Subject: |FAILURE| pw157320 [PATCH] app/crypto-perf: add ECDSA P192/P224/P521
Date: Tue, 07 Oct 2025 23:26:05 -0700 (PDT)	[thread overview]
Message-ID: <68e603fd.050a0220.3081a1.b1cdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251008054059.3934959-1-rchiluka@marvell.com>

Test-Label: iol-intel-Functional
Test-Status: FAILURE
http://dpdk.org/patch/157320

_Functional Testing issues_

Submitter: Rupesh Chiluka <rchiluka@marvell.com>
Date: Wednesday, October 08 2025 05:40:59 
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: master
  CommitID:2aa7141a4e2c78e3cce03dbd613532a2166123c1

157320 --> functional testing issues

Upstream job id: Template-DTS-Pipeline#248433

Test environment and result as below:

Ubuntu 24.04 LTS
Kernel: 6.8.0-44-generic
Compiler: gcc 13.2.0
NIC: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ 40 Mbps

Aggregate Results by Test Suite
+--------------------+--------+
|     Test Suite     | Result |
+====================+========+
| blocklist          |  PASS  |
+--------------------+--------+
| promisc_support    |  PASS  |
+--------------------+--------+
| uni_pkt            |  PASS  |
+--------------------+--------+
| dynamic_config     |  PASS  |
+--------------------+--------+
| dynamic_queue_conf |  PASS  |
+--------------------+--------+
| hello_world        |  PASS  |
+--------------------+--------+
| l2fwd              |  PASS  |
+--------------------+--------+
| softnic            |  PASS  |
+--------------------+--------+
| vlan               |  PASS  |
+--------------------+--------+


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 |  FAIL  |
+----------------------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-10-08  6:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251008054059.3934959-1-rchiluka@marvell.com>
2025-10-08  5:07 ` |SUCCESS| pw157320 [PATCH] app/crypto-perf: add ECDSA P192/P224/P521 support qemudev
2025-10-08  5:12 ` qemudev
2025-10-08  5:42 ` checkpatch
2025-10-08  6:13 ` |PENDING| pw157320 [PATCH] app/crypto-perf: add ECDSA P192/P224/P521 dpdklab
2025-10-08  6:17 ` |SUCCESS| " dpdklab
2025-10-08  6:20 ` dpdklab
2025-10-08  6:25 ` dpdklab
2025-10-08  6:26 ` dpdklab [this message]
2025-10-08  6:38 ` |FAILURE| " dpdklab
2025-10-08  6:43 ` |PENDING| " dpdklab
2025-10-08  6:57 ` |SUCCESS| " dpdklab
2025-10-08  7:02 ` |PENDING| " dpdklab
2025-10-08  7:04 ` |SUCCESS| " dpdklab
2025-10-08  7:42 ` dpdklab
2025-10-08  8:10 ` dpdklab
2025-10-08  8:46 ` |FAILURE| " 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=68e603fd.050a0220.3081a1.b1cdSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=gakhil@marvell.com \
    --cc=rchiluka@marvell.com \
    --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).