From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw153824 [PATCH] crypto/virtio: fix driver ID for virtio
Date: Thu, 29 May 2025 04:22:05 -0700 (PDT) [thread overview]
Message-ID: <6838435d.050a0220.e21cb.336eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250528105347.2014993-1-rmudimadugul@marvell.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/153824
_Functional Testing PASS_
Submitter: Rajesh Mudimadugula <rmudimadugul@marvell.com>
Date: Wednesday, May 28 2025 10:53:47
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d5968c8a2b355a083db1d2f4f00334760389b54c
153824 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#228322
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
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/33267/
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-05-29 11:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250528105347.2014993-1-rmudimadugul@marvell.com>
2025-05-28 10:19 ` qemudev
2025-05-28 10:23 ` qemudev
2025-05-28 10:54 ` checkpatch
2025-05-28 12:23 ` 0-day Robot
2025-05-29 10:43 ` dpdklab
2025-05-29 11:22 ` dpdklab [this message]
2025-05-29 11:38 ` |PENDING| " dpdklab
2025-05-29 13:17 ` |SUCCESS| " dpdklab
2025-05-29 13:22 ` dpdklab
2025-05-29 13:22 ` dpdklab
2025-05-29 15:14 ` |PENDING| " dpdklab
2025-05-29 21:56 ` |SUCCESS| " dpdklab
2025-05-29 22:00 ` dpdklab
2025-05-29 22:02 ` 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=6838435d.050a0220.e21cb.336eSMTPIN_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).