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| pw156269-156270 [PATCH] [v3,2/2] net/mlx5: improve debug d
Date: Fri, 29 Aug 2025 08:41:29 -0700 (PDT)	[thread overview]
Message-ID: <68b1ca29.050a0220.2401a8.77e4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250829144954.2576-2-mosesyyoung@gmail.com>

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

_Functional Testing PASS_

Submitter: Moses Young <mosesyyoung@gmail.com>
Date: Friday, August 29 2025 14:49:53 
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: master
  CommitID:507dd6a18ebcae562fd0539bddbf499a4b891bb7

156269-156270 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#242378

Test environment and result as below:

Ubuntu 24.04 LTS
Kernel: 6.8.0-44-generic
Compiler: gcc 13.2.0
NIC: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ 40 Mbps

Aggregate Results by Test Suite
+--------------------+--------+
|     Test Suite     | Result |
+====================+========+
| blocklist          |  PASS  |
+--------------------+--------+
| promisc_support    |  PASS  |
+--------------------+--------+
| uni_pkt            |  PASS  |
+--------------------+--------+
| dynamic_config     |  PASS  |
+--------------------+--------+
| dynamic_queue_conf |  PASS  |
+--------------------+--------+
| hello_world        |  PASS  |
+--------------------+--------+
| l2fwd              |  PASS  |
+--------------------+--------+
| softnic            |  PASS  |
+--------------------+--------+
| vlan               |  PASS  |
+--------------------+--------+


Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 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/33991/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-08-29 15:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250829144954.2576-2-mosesyyoung@gmail.com>
2025-08-29 14:20 ` |SUCCESS| pw156269-156270 [PATCH v3 2/2] net/mlx5: improve debug dump file path handling qemudev
2025-08-29 14:25 ` qemudev
2025-08-29 14:48 ` |SUCCESS| pw156270 " checkpatch
2025-08-29 15:19 ` |PENDING| pw156269-156270 [PATCH] [v3,2/2] net/mlx5: improve debug d dpdklab
2025-08-29 15:23 ` dpdklab
2025-08-29 15:27 ` |SUCCESS| " dpdklab
2025-08-29 15:27 ` |PENDING| " dpdklab
2025-08-29 15:28 ` |SUCCESS| " dpdklab
2025-08-29 15:32 ` |PENDING| " dpdklab
2025-08-29 15:41 ` dpdklab [this message]
2025-08-29 15:43 ` |SUCCESS| " dpdklab
2025-08-29 15:44 ` dpdklab
2025-08-29 15:45 ` dpdklab
2025-08-29 15:54 ` dpdklab
2025-08-29 15:59 ` dpdklab
2025-08-29 16:05 ` dpdklab
2025-08-29 16:26 ` dpdklab
2025-08-29 18:24 ` |SUCCESS| pw156270 [PATCH v3 2/2] net/mlx5: improve debug dump file path handling 0-day Robot

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=68b1ca29.050a0220.2401a8.77e4SMTPIN_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).