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: |PENDING| pw155980 [PATCH] app/crypto-perf: add ECDSA P384 support
Date: Mon, 18 Aug 2025 22:09:56 -0700 (PDT)	[thread overview]
Message-ID: <68a40724.170a0220.1960da.c9beSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250819041517.1638717-1-rchiluka@marvell.com>

Test-Label: iol-compile-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/155980

_Testing pending_

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

155980 --> testing pending

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

Test environment and result as below:

+---------------------+--------------------+
|     Environment     | dpdk_meson_compile |
+=====================+====================+
| Ubuntu 20.04        | PEND               |
+---------------------+--------------------+
| Fedora Linux 42     | PEND               |
+---------------------+--------------------+
| Debian GNU/Linux 12 | PEND               |
+---------------------+--------------------+
| CentOS Stream 9     | PEND               |
+---------------------+--------------------+
| Ubuntu 22.04        | PEND               |
+---------------------+--------------------+
| CentOS Stream 10    | PEND               |
+---------------------+--------------------+


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

Fedora Linux 42
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 15.1.1 20250521 (Red Hat 15.1.1-2)

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

CentOS Stream 9
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-7)

Ubuntu 22.04
	Kernel: 5.4
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

CentOS Stream 10
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-8)

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

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  5:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250819041517.1638717-1-rchiluka@marvell.com>
2025-08-19  4:05 ` |SUCCESS| " qemudev
2025-08-19  4:10 ` qemudev
2025-08-19  4:14 ` |WARNING| " checkpatch
2025-08-19  5:02 ` |SUCCESS| " dpdklab
2025-08-19  5:02 ` dpdklab
2025-08-19  5:08 ` |PENDING| " dpdklab
2025-08-19  5:09 ` |SUCCESS| " dpdklab
2025-08-19  5:09 ` dpdklab [this message]
2025-08-19  5:17 ` dpdklab
2025-08-19  5:19 ` dpdklab
2025-08-19  5:22 ` dpdklab
2025-08-19  5:28 ` 0-day Robot
2025-08-19  5:30 ` dpdklab
2025-08-19  5:37 ` dpdklab
2025-08-19  5:39 ` dpdklab
2025-08-19  5:40 ` dpdklab
2025-08-19  5:40 ` dpdklab
2025-08-19  6:55 ` dpdklab
2025-08-19 14:21 ` dpdklab
2025-08-19 16:10 ` dpdklab
2025-08-19 16:17 ` dpdklab
2025-08-19 16:21 ` dpdklab
2025-08-19 16:28 ` 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=68a40724.170a0220.1960da.c9beSMTPIN_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).