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: |SUCCESS| pw152760-152761 [PATCH] [2/2] crypto/virtio: fix cipher da
Date: Thu, 03 Apr 2025 11:33:38 -0700 (PDT)	[thread overview]
Message-ID: <67eed482.050a0220.d94e2.2aabSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250403122603.3508135-1-rmudimadugul@marvell.com>

Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/152761

_Testing PASS_

Submitter: Rajesh Mudimadugula <rmudimadugul@marvell.com>
Date: Thursday, April 03 2025 12:26:03 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:edd3f4b1265e6da707c46ca9b6c39d332647baea

152760-152761 --> testing pass

Upstream job id: ACVP-FIPS-testing#9445

Test environment and result as below:

+--------------------+----------------------+----------------------+
|    Environment     | compressdev_zlib_pmd | dpdk_fips_validation |
+====================+======================+======================+
| Ubuntu 22.04 (ARM) | PASS                 | SKIPPED              |
+--------------------+----------------------+----------------------+
| Ubuntu 22.04       | PASS                 | SKIPPED              |
+--------------------+----------------------+----------------------+
| Ubuntu 20.04       | SKIPPED              | PASS                 |
+--------------------+----------------------+----------------------+


Ubuntu 22.04 (ARM)
	Kernel: 5.15.0-97-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 22.04
	Kernel: 5.15.0-100-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 20.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2025-04-03 18:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250403122603.3508135-1-rmudimadugul@marvell.com>
2025-04-03 11:51 ` |SUCCESS| pw152760-152761 [PATCH 2/2] crypto/virtio: fix cipher data src length qemudev
2025-04-03 11:55 ` qemudev
2025-04-03 12:26 ` |SUCCESS| pw152761 " checkpatch
2025-04-03 13:27 ` |SUCCESS| pw152760-152761 [PATCH] [2/2] crypto/virtio: fix cipher da dpdklab
2025-04-03 13:27 ` dpdklab
2025-04-03 13:30 ` |PENDING| " dpdklab
2025-04-03 13:31 ` |SUCCESS| " dpdklab
2025-04-03 13:35 ` dpdklab
2025-04-03 13:42 ` |SUCCESS| pw152761 [PATCH 2/2] crypto/virtio: fix cipher data src length 0-day Robot
2025-04-03 13:43 ` |SUCCESS| pw152760-152761 [PATCH] [2/2] crypto/virtio: fix cipher da dpdklab
2025-04-03 13:52 ` dpdklab
2025-04-03 13:55 ` |PENDING| " dpdklab
2025-04-03 13:56 ` |SUCCESS| " dpdklab
2025-04-03 13:56 ` dpdklab
2025-04-03 14:01 ` dpdklab
2025-04-03 14:12 ` |PENDING| " dpdklab
2025-04-03 14:37 ` |SUCCESS| " dpdklab
2025-04-03 15:29 ` dpdklab
2025-04-03 16:00 ` dpdklab
2025-04-03 16:44 ` dpdklab
2025-04-03 16:50 ` dpdklab
2025-04-03 18:33 ` dpdklab [this message]
2025-04-03 19:54 ` dpdklab
2025-04-04  2:08 ` dpdklab
2025-04-04  2:30 ` dpdklab
2025-04-04 16:56 ` 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=67eed482.050a0220.d94e2.2aabSMTPIN_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).