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| pw154367 [PATCH] crypto/qat: fix out-of-place chain/cipher
Date: Thu, 12 Jun 2025 05:12:27 -0700 (PDT)	[thread overview]
Message-ID: <684ac42b.050a0220.14cc3a.3d79SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250612101414.240641-1-radu.nicolau@intel.com>

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/154367

_Functional Testing PASS_

Submitter: Radu Nicolau <radu.nicolau@intel.com>
Date: Thursday, June 12 2025 10:14:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:de7d4a7a657b22a366caa2e14723cd03d40bdb7c

154367 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#230358

Test environment and result as below:

Ubuntu 24.04 LTS
Kernel: 6.8.0-55-generic
Compiler: gcc 13.3.0
NIC: Intel Corporation 4xxx Series QAT 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/33395/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-06-12 12:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250612101414.240641-1-radu.nicolau@intel.com>
2025-06-12  9:39 ` |SUCCESS| pw154367 [PATCH] crypto/qat: fix out-of-place chain/cipher/auth headers qemudev
2025-06-12  9:43 ` qemudev
2025-06-12 10:14 ` checkpatch
2025-06-12 11:39 ` 0-day Robot
2025-06-12 11:56 ` |SUCCESS| pw154367 [PATCH] crypto/qat: fix out-of-place chain/cipher dpdklab
2025-06-12 11:58 ` dpdklab
2025-06-12 12:01 ` dpdklab
2025-06-12 12:02 ` |PENDING| " dpdklab
2025-06-12 12:12 ` dpdklab [this message]
2025-06-12 12:23 ` |SUCCESS| " dpdklab
2025-06-12 12:24 ` |PENDING| " dpdklab
2025-06-12 12:29 ` |SUCCESS| " dpdklab
2025-06-12 12:43 ` |WARNING| " dpdklab
2025-06-12 12:43 ` dpdklab
2025-06-12 12:54 ` |FAILURE| " dpdklab
2025-06-12 13:01 ` |PENDING| " dpdklab
2025-06-12 13:02 ` |FAILURE| " dpdklab
2025-06-12 13:08 ` |SUCCESS| " dpdklab
2025-06-12 13:15 ` |PENDING| " dpdklab
2025-06-12 14:03 ` |WARNING| " dpdklab
2025-06-12 14:22 ` |SUCCESS| " dpdklab
2025-06-12 17:02 ` dpdklab
2025-06-12 23:51 ` 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=684ac42b.050a0220.14cc3a.3d79SMTPIN_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).