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| pw153161-153162 [PATCH] [2/2] net/mlx5: fix counter servic
Date: Sat, 26 Apr 2025 20:32:56 -0700 (PDT)	[thread overview]
Message-ID: <680da568.170a0220.359925.2842SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250425194105.39401-3-dsosnowski@nvidia.com>

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

_Functional Testing PASS_

Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Friday, April 25 2025 19:41:05 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:edd3f4b1265e6da707c46ca9b6c39d332647baea

153161-153162 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#223145

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

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-27  3:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250425194105.39401-3-dsosnowski@nvidia.com>
2025-04-25 19:37 ` |SUCCESS| pw153161-153162 [PATCH 2/2] net/mlx5: fix counter service thread init qemudev
2025-04-25 19:42 ` qemudev
2025-04-25 19:42 ` |SUCCESS| pw153162 " checkpatch
2025-04-25 21:04 ` 0-day Robot
2025-04-27  3:08 ` |SUCCESS| pw153161-153162 [PATCH] [2/2] net/mlx5: fix counter servic dpdklab
2025-04-27  3:16 ` dpdklab
2025-04-27  3:26 ` dpdklab
2025-04-27  3:32 ` dpdklab [this message]
2025-04-27  3:37 ` dpdklab
2025-04-27  3:52 ` dpdklab
2025-04-27  3:52 ` dpdklab
2025-04-27  4:06 ` dpdklab
2025-04-27  4:07 ` dpdklab
2025-04-27  4:07 ` dpdklab
2025-04-27  4:08 ` dpdklab
2025-04-27  4:21 ` dpdklab
2025-04-27  4:41 ` dpdklab
2025-04-27  4:42 ` |PENDING| " dpdklab
2025-04-27  4:42 ` dpdklab
2025-04-27  6:42 ` |SUCCESS| " dpdklab
2025-04-27  6:55 ` dpdklab
2025-04-27  6:56 ` dpdklab
2025-04-27  9:25 ` dpdklab
2025-04-27 10:00 ` dpdklab
2025-04-27 11:19 ` 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=680da568.170a0220.359925.2842SMTPIN_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).