From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw155544 [PATCH] app/crypto-perf: Only run AEAD decrypt wi
Date: Mon, 28 Jul 2025 15:46:29 -0700 (PDT) [thread overview]
Message-ID: <6887fdc5.050a0220.3533ac.ce33SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250728080621.1241228-1-emma.finn@intel.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/155544
_Testing PASS_
Submitter: Emma Finn <emma.finn@intel.com>
Date: Monday, July 28 2025 08:06:21
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:390cb3d4ea2f9139e18c7541ec68d269bfe3dc37
155544 --> testing pass
Upstream job id: ACVP-FIPS-testing#10631
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33757/
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-07-28 22:46 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250728080621.1241228-1-emma.finn@intel.com>
2025-07-28 7:34 ` |SUCCESS| pw155544 [PATCH] app/crypto-perf: Only run AEAD decrypt with valid test vector file qemudev
2025-07-28 7:39 ` qemudev
2025-07-28 8:05 ` checkpatch
2025-07-28 9:24 ` 0-day Robot
2025-07-28 16:27 ` |SUCCESS| pw155544 [PATCH] app/crypto-perf: Only run AEAD decrypt wi dpdklab
2025-07-28 16:30 ` dpdklab
2025-07-28 16:30 ` |FAILURE| " dpdklab
2025-07-28 16:31 ` dpdklab
2025-07-28 16:48 ` dpdklab
2025-07-28 16:51 ` |SUCCESS| " dpdklab
2025-07-28 17:27 ` dpdklab
2025-07-28 17:29 ` dpdklab
2025-07-28 17:34 ` |PENDING| " dpdklab
2025-07-28 17:35 ` |SUCCESS| " dpdklab
2025-07-28 17:35 ` |FAILURE| " dpdklab
2025-07-28 17:47 ` |PENDING| " dpdklab
2025-07-28 18:02 ` |FAILURE| " dpdklab
2025-07-28 18:03 ` |SUCCESS| " dpdklab
2025-07-28 18:07 ` |PENDING| " dpdklab
2025-07-28 18:08 ` dpdklab
2025-07-28 18:16 ` |SUCCESS| " dpdklab
2025-07-28 18:33 ` |PENDING| " dpdklab
2025-07-28 18:36 ` |SUCCESS| " dpdklab
2025-07-28 18:42 ` |FAILURE| " dpdklab
2025-07-28 18:43 ` |PENDING| " dpdklab
2025-07-28 19:09 ` |SUCCESS| " dpdklab
2025-07-28 19:17 ` dpdklab
2025-07-28 19:25 ` dpdklab
2025-07-28 19:42 ` dpdklab
2025-07-28 19:43 ` dpdklab
2025-07-28 19:57 ` dpdklab
2025-07-28 20:16 ` dpdklab
2025-07-28 20:31 ` dpdklab
2025-07-28 20:37 ` |FAILURE| " dpdklab
2025-07-28 21:05 ` |SUCCESS| " dpdklab
2025-07-28 21:38 ` |PENDING| " dpdklab
2025-07-28 21:44 ` |FAILURE| " dpdklab
2025-07-28 22:31 ` |SUCCESS| " dpdklab
2025-07-28 22:46 ` dpdklab [this message]
2025-07-29 0:00 ` dpdklab
2025-07-29 0:07 ` dpdklab
2025-07-29 0:07 ` dpdklab
2025-07-29 3:58 ` 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=6887fdc5.050a0220.3533ac.ce33SMTPIN_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).