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| pw154449 [PATCH] common/mlx5: fix extraction of auxiliary
Date: Sun, 15 Jun 2025 01:48:44 -0700 (PDT)	[thread overview]
Message-ID: <684e88ec.050a0220.16460.fb40SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250615074129.52396-1-getelson@nvidia.com>

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

_Functional Testing PASS_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Sunday, June 15 2025 07:41:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:77ba8d12251b203a4ec69a569c2f2f07edb7b1e8

154449 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#230872

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

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-15  8:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250615074129.52396-1-getelson@nvidia.com>
2025-06-15  7:13 ` |SUCCESS| pw154449 [PATCH] common/mlx5: fix extraction of auxiliary network device name qemudev
2025-06-15  7:17 ` qemudev
2025-06-15  7:42 ` checkpatch
2025-06-15  8:38 ` |SUCCESS| pw154449 [PATCH] common/mlx5: fix extraction of auxiliary dpdklab
2025-06-15  8:39 ` dpdklab
2025-06-15  8:43 ` |PENDING| " dpdklab
2025-06-15  8:46 ` |SUCCESS| " dpdklab
2025-06-15  8:48 ` dpdklab [this message]
2025-06-15  8:53 ` |FAILURE| " dpdklab
2025-06-15  8:54 ` |PENDING| " dpdklab
2025-06-15  8:58 ` |SUCCESS| " dpdklab
2025-06-15  9:00 ` |PENDING| " dpdklab
2025-06-15  9:03 ` |FAILURE| " dpdklab
2025-06-15  9:12 ` |SUCCESS| " dpdklab
2025-06-15  9:19 ` |SUCCESS| pw154449 [PATCH] common/mlx5: fix extraction of auxiliary network device name 0-day Robot
2025-06-15  9:59 ` |SUCCESS| pw154449 [PATCH] common/mlx5: fix extraction of auxiliary dpdklab
2025-06-15 10:37 ` dpdklab
2025-06-15 10:46 ` |FAILURE| " dpdklab
2025-06-15 10:58 ` |SUCCESS| " dpdklab
2025-06-15 11:13 ` dpdklab
2025-06-15 13:55 ` 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=684e88ec.050a0220.16460.fb40SMTPIN_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).