From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw154452 [PATCH] [v3] app/crypto-perf: add support for RSA
Date: Tue, 24 Jun 2025 11:35:30 -0700 (PDT) [thread overview]
Message-ID: <685aeff2.170a0220.104e5.10b0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250616060103.2503415-1-ssarananaga@marvell.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/154452
_Functional Testing PASS RETEST #2_
Submitter: Sucharitha Sarananaga <ssarananaga@marvell.com>
Date: Monday, June 16 2025 06:01:03
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6890ee7ba76e92745d6c61b3b6b9d757ebaaa89d
154452 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#232780
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Intel Corporation QAT 8970 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/33416/
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:[~2025-06-24 18:35 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250616060103.2503415-1-ssarananaga@marvell.com>
2025-06-16 5:33 ` |SUCCESS| pw154452 [PATCH v3] app/crypto-perf: add support for RSA decrypt qemudev
2025-06-16 5:37 ` qemudev
2025-06-16 6:01 ` checkpatch
2025-06-16 6:44 ` |FAILURE| pw154452 [PATCH] [v3] app/crypto-perf: add support for RSA dpdklab
2025-06-16 6:46 ` |SUCCESS| " dpdklab
2025-06-16 6:49 ` |FAILURE| " dpdklab
2025-06-16 6:54 ` |SUCCESS| " dpdklab
2025-06-16 6:57 ` |FAILURE| " dpdklab
2025-06-16 6:58 ` |PENDING| " dpdklab
2025-06-16 7:00 ` |SUCCESS| " dpdklab
2025-06-16 7:05 ` |SUCCESS| pw154452 [PATCH v3] app/crypto-perf: add support for RSA decrypt 0-day Robot
2025-06-16 7:11 ` |SUCCESS| pw154452 [PATCH] [v3] app/crypto-perf: add support for RSA dpdklab
2025-06-16 7:24 ` dpdklab
2025-06-16 7:56 ` dpdklab
2025-06-16 7:59 ` |PENDING| " dpdklab
2025-06-16 8:31 ` |SUCCESS| " dpdklab
2025-06-16 8:34 ` dpdklab
2025-06-16 8:35 ` dpdklab
2025-06-16 9:21 ` dpdklab
2025-06-16 9:21 ` dpdklab
2025-06-16 9:22 ` dpdklab
2025-06-16 10:58 ` |FAILURE| " dpdklab
2025-06-16 14:03 ` |SUCCESS| " dpdklab
2025-06-16 14:38 ` dpdklab
2025-06-17 22:06 ` |FAILURE| " dpdklab
2025-06-17 22:48 ` dpdklab
2025-06-17 23:03 ` dpdklab
2025-06-18 0:18 ` dpdklab
2025-06-18 2:45 ` dpdklab
2025-06-18 14:29 ` |SUCCESS| " dpdklab
2025-06-19 3:44 ` |FAILURE| " dpdklab
2025-06-19 3:50 ` dpdklab
2025-06-24 13:27 ` |SUCCESS| pw154452 [PATCH v3] app/crypto-perf: add support for RSA decrypt qemudev
2025-06-24 13:32 ` qemudev
2025-06-24 14:15 ` qemudev
2025-06-24 14:20 ` qemudev
2025-06-24 16:30 ` |SUCCESS| pw154452 [PATCH] [v3] app/crypto-perf: add support for RSA dpdklab
2025-06-24 16:47 ` |PENDING| " dpdklab
2025-06-24 16:52 ` |SUCCESS| " dpdklab
2025-06-24 17:13 ` dpdklab
2025-06-24 17:26 ` |PENDING| " dpdklab
2025-06-24 17:53 ` |SUCCESS| " dpdklab
2025-06-24 18:35 ` dpdklab [this message]
2025-06-24 20:10 ` |PENDING| " dpdklab
2025-06-24 20:40 ` |FAILURE| " dpdklab
2025-06-24 20:40 ` dpdklab
2025-06-24 20:54 ` dpdklab
2025-06-24 20:54 ` dpdklab
2025-06-24 21:34 ` |SUCCESS| " dpdklab
2025-06-24 23:59 ` |PENDING| " dpdklab
2025-06-25 1:04 ` |SUCCESS| " dpdklab
2025-06-25 2:00 ` dpdklab
2025-06-25 2:00 ` dpdklab
2025-06-25 2:02 ` dpdklab
2025-06-25 2:08 ` |WARNING| " dpdklab
2025-06-25 2:09 ` dpdklab
2025-06-25 2:11 ` dpdklab
2025-06-25 2:15 ` dpdklab
2025-06-25 4:21 ` |SUCCESS| " 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=685aeff2.170a0220.104e5.10b0SMTPIN_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).