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| pw157229 [PATCH] app/crypto-perf: add ECDSA P192/P224/P521
Date: Sun, 05 Oct 2025 15:15:02 -0700 (PDT)	[thread overview]
Message-ID: <68e2ede6.170a0220.1a7bf0.fb2dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251003034233.2964182-1-rchiluka@marvell.com>

Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/157229

_Testing issues_

Submitter: Rupesh Chiluka <rchiluka@marvell.com>
Date: Friday, October 03 2025 03:42:33 
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: master
  CommitID:caa17cb4b057a31ee04067459fe543f7d7ae1079

157229 --> testing issues

Upstream job id: Generic-DPDK-Compile-Meson#431234

Test environment and result as below:

+------------------------------+--------------------+
|         Environment          | dpdk_meson_compile |
+==============================+====================+
| Red Hat Enterprise Linux 9.5 | PEND               |
+------------------------------+--------------------+
| Ubuntu 20.04                 | PEND               |
+------------------------------+--------------------+
| Debian GNU/Linux 12          | PEND               |
+------------------------------+--------------------+
| Fedora Linux 42              | PEND               |
+------------------------------+--------------------+


Red Hat Enterprise Linux 9.5
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)

Ubuntu 20.04
	Kernel: 5.15
	Compiler: aarch64-linux-gnu-gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Debian GNU/Linux 12
	Kernel: 5.4
	Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0

Fedora Linux 42
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 15.2.1 20250808 (Red Hat 15.2.1-1)

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

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-05 22:15 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251003034233.2964182-1-rchiluka@marvell.com>
2025-10-03  3:09 ` |SUCCESS| pw157229 [PATCH] app/crypto-perf: add ECDSA P192/P224/P521 support qemudev
2025-10-03  3:14 ` qemudev
2025-10-03  3:44 ` checkpatch
2025-10-03  4:17 ` |FAILURE| pw157229 [PATCH] app/crypto-perf: add ECDSA P192/P224/P521 dpdklab
2025-10-03  4:21 ` |SUCCESS| " dpdklab
2025-10-03  4:51 ` |FAILURE| " dpdklab
2025-10-03  4:57 ` |SUCCESS| " dpdklab
2025-10-03  4:59 ` dpdklab
2025-10-03  5:10 ` |FAILURE| " dpdklab
2025-10-03  5:16 ` dpdklab
2025-10-03  5:18 ` dpdklab
2025-10-03  5:36 ` |PENDING| " dpdklab
2025-10-03  5:37 ` |WARNING| " dpdklab
2025-10-03  5:46 ` |FAILURE| " dpdklab
2025-10-03  5:46 ` dpdklab
2025-10-03  5:47 ` dpdklab
2025-10-03  5:47 ` dpdklab
2025-10-03  5:48 ` dpdklab
2025-10-03  5:50 ` dpdklab
2025-10-03  5:51 ` dpdklab
2025-10-03  5:52 ` dpdklab
2025-10-03  5:52 ` dpdklab
2025-10-03  5:53 ` dpdklab
2025-10-03  5:55 ` dpdklab
2025-10-03  5:56 ` dpdklab
2025-10-03  5:57 ` dpdklab
2025-10-03  5:59 ` dpdklab
2025-10-03  6:59 ` |WARNING| " dpdklab
2025-10-03  7:00 ` |SUCCESS| " dpdklab
2025-10-03  7:10 ` |FAILURE| " dpdklab
2025-10-03  8:09 ` dpdklab
2025-10-04  1:04 ` dpdklab
2025-10-05 21:31 ` dpdklab
2025-10-05 22:15 ` dpdklab [this message]
2025-10-05 23:23 ` dpdklab
2025-10-05 23:28 ` dpdklab
2025-10-05 23:44 ` dpdklab
2025-10-06  0:13 ` dpdklab
2025-10-06  0:14 ` dpdklab
2025-10-06  0:14 ` dpdklab
2025-10-06  0:26 ` 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=68e2ede6.170a0220.1a7bf0.fb2dSMTPIN_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).