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| pw153890-153914 [PATCH] [v4,25/25] net/intel: add common T
Date: Wed, 04 Jun 2025 09:42:48 -0700 (PDT)	[thread overview]
Message-ID: <68407788.170a0220.176422.d052SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <150e8c6ff6c3730f5c9ed78477d0b615c7f35a1a.1748612804.git.anatoly.burakov@intel.com>

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

_Functional Testing PASS_

Submitter: Burakov, Anatoly <anatoly.burakov@intel.com>
Date: Friday, May 30 2025 13:57:21 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:466db466e2938c0d4e7f3dd75435483133f98770

153890-153914 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#228631

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  |
+----------------------------+--------+


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/33290/

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-04 16:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <150e8c6ff6c3730f5c9ed78477d0b615c7f35a1a.1748612804.git.anatoly.burakov@intel.com>
2025-05-30 13:28 ` |SUCCESS| pw153890-153914 [PATCH v4 25/25] net/intel: add common Tx mbuf recycle qemudev
2025-05-30 13:32 ` qemudev
2025-05-30 14:03 ` |SUCCESS| pw153914 " checkpatch
2025-05-30 14:53 ` |PENDING| pw153890-153914 [PATCH] [v4,25/25] net/intel: add common T dpdklab
2025-05-30 15:01 ` |FAILURE| pw153914 [PATCH v4 25/25] net/intel: add common Tx mbuf recycle 0-day Robot
2025-05-30 15:06 ` |PENDING| pw153890-153914 [PATCH] [v4,25/25] net/intel: add common T dpdklab
2025-05-30 15:07 ` |SUCCESS| " dpdklab
2025-05-30 15:25 ` |PENDING| " dpdklab
2025-05-30 15:27 ` |SUCCESS| " dpdklab
2025-05-30 15:27 ` dpdklab
2025-05-30 15:44 ` dpdklab
2025-05-30 15:44 ` dpdklab
2025-05-30 15:51 ` dpdklab
2025-05-30 16:38 ` dpdklab
2025-05-30 18:39 ` |PENDING| " dpdklab
2025-05-30 19:27 ` |WARNING| " dpdklab
2025-05-30 21:55 ` |SUCCESS| " dpdklab
2025-05-30 22:33 ` dpdklab
2025-05-30 23:59 ` |WARNING| " dpdklab
2025-05-31  0:04 ` dpdklab
2025-05-31  9:14 ` |SUCCESS| " dpdklab
2025-05-31  9:23 ` dpdklab
2025-05-31 10:41 ` dpdklab
2025-06-04 16:42 ` dpdklab [this message]

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=68407788.170a0220.176422.d052SMTPIN_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).