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| pw159354 [PATCH] [1/1] net/mlx5: fix memoy leak after devi
Date: Thu, 18 Dec 2025 03:31:49 -0800 (PST)	[thread overview]
Message-ID: <6943e625.170a0220.75f99.b9c4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1766050280-21036-1-git-send-email-wangyunjian@huawei.com>

Test-Label: iol-mellanox-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/159354

_Functional Testing PASS_

Submitter: Yunjian Wang <wangyunjian@huawei.com>
Date: Thursday, December 18 2025 09:31:20 
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: master
  CommitID:2815d5065694eb9d0b43c312d17a00d2356e36f1

159354 --> functional testing pass

Upstream job id: Template-DPDK-DTS-Pipeline#3908

Test environment and result as below:

Ubuntu 24.04
Kernel: 6.8.0-55-generic
Compiler: gcc 13.3.0
NIC: Mellanox ConnectX-5 100000 Mbps

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


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34786/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-12-18 11:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1766050280-21036-1-git-send-email-wangyunjian@huawei.com>
2025-12-18  9:30 ` |WARNING| pw159354 [PATCH 1/1] net/mlx5: fix memoy leak after device spawn failure checkpatch
2025-12-18 10:02 ` |SUCCESS| " qemudev
2025-12-18 10:07 ` qemudev
2025-12-18 10:49 ` 0-day Robot
2025-12-18 10:49 ` 0-day Robot
2025-12-18 11:31 ` dpdklab [this message]
2025-12-18 11:36 ` |SUCCESS| pw159354 [PATCH] [1/1] net/mlx5: fix memoy leak after devi dpdklab
2025-12-18 11:37 ` |PENDING| " dpdklab
2025-12-18 11:41 ` |SUCCESS| " dpdklab
2025-12-18 11:48 ` |PENDING| " dpdklab
2025-12-18 11:52 ` |SUCCESS| " dpdklab
2025-12-18 11:55 ` dpdklab
2025-12-18 11:55 ` dpdklab
2025-12-18 12:10 ` |PENDING| " dpdklab
2025-12-18 12:14 ` |SUCCESS| " dpdklab
2025-12-18 12:26 ` |PENDING| " dpdklab
2025-12-18 12:51 ` |SUCCESS| " dpdklab
2025-12-18 12:57 ` dpdklab
2025-12-18 12:59 ` dpdklab
2025-12-18 15:11 ` dpdklab
2025-12-18 15:53 ` dpdklab
2025-12-19  1:23 ` 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=6943e625.170a0220.75f99.b9c4SMTPIN_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).