From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw159355 [PATCH] [v2] net/mlx5: fix memoy leak after devic
Date: Thu, 18 Dec 2025 06:40:12 -0800 (PST) [thread overview]
Message-ID: <6944124c.050a0220.1fa242.d60cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1766055446-41476-1-git-send-email-wangyunjian@huawei.com>
Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/159355
_Testing pending_
Submitter: Yunjian Wang <wangyunjian@huawei.com>
Date: Thursday, December 18 2025 10:57:26
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: master
CommitID:2815d5065694eb9d0b43c312d17a00d2356e36f1
159355 --> testing pending
Upstream job id: Generic-VM-DPDK-Compile-Meson#40358
Test environment and result as below:
+-------------------------------+--------------------+-------------------+------------------+
| Environment | dpdk_meson_compile | dpdk_msvc_compile | dpdk_compile_ovs |
+===============================+====================+===================+==================+
| Ubuntu 24.04 | PEND | SKIPPED | PEND |
+-------------------------------+--------------------+-------------------+------------------+
| FreeBSD 14.2 | PASS | SKIPPED | SKIPPED |
+-------------------------------+--------------------+-------------------+------------------+
| Debian GNU/Linux 12 | PEND | SKIPPED | SKIPPED |
+-------------------------------+--------------------+-------------------+------------------+
| CentOS Stream 10 | PEND | SKIPPED | SKIPPED |
+-------------------------------+--------------------+-------------------+------------------+
| Fedora Linux 42 | PEND | SKIPPED | PEND |
+-------------------------------+--------------------+-------------------+------------------+
| openSUSE Leap 15.6 | PEND | SKIPPED | SKIPPED |
+-------------------------------+--------------------+-------------------+------------------+
| Ubuntu 22.04 | PEND | SKIPPED | SKIPPED |
+-------------------------------+--------------------+-------------------+------------------+
| Red Hat Enterprise Linux 8.10 | PEND | SKIPPED | SKIPPED |
+-------------------------------+--------------------+-------------------+------------------+
| Red Hat Enterprise Linux 9.7 | PEND | SKIPPED | SKIPPED |
+-------------------------------+--------------------+-------------------+------------------+
| Alpine Linux 3.23.0 | PEND | SKIPPED | SKIPPED |
+-------------------------------+--------------------+-------------------+------------------+
| Ubuntu 20.04 | PEND | SKIPPED | SKIPPED |
+-------------------------------+--------------------+-------------------+------------------+
| CentOS Stream 9 | PEND | SKIPPED | SKIPPED |
+-------------------------------+--------------------+-------------------+------------------+
| Windows Server 2022 | SKIPPED | PEND | SKIPPED |
+-------------------------------+--------------------+-------------------+------------------+
Ubuntu 24.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
FreeBSD 14.2
Kernel: 14.2-RELEASE
Compiler: clang 18.1.6
Debian GNU/Linux 12
Kernel: 5.15
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
CentOS Stream 10
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.3.1 20251022 (Red Hat 14.3.1-4)
Fedora Linux 42
Kernel: 5.15
Compiler: clang gcc (GCC) 15.2.1 20251111 (Red Hat 15.2.1-4)
openSUSE Leap 15.6
Kernel: 5.15
Compiler: gcc gcc (SUSE Linux) 7.5.0
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0
Red Hat Enterprise Linux 8.10
Kernel: 5.15
Compiler: gcc gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-22)
Red Hat Enterprise Linux 9.7
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11)
Alpine Linux 3.23.0
Kernel: 5.15
Compiler: gcc gcc (Alpine 15.2.0) 15.2.0
Ubuntu 20.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
CentOS Stream 9
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-14)
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34787/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-12-18 14:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1766055446-41476-1-git-send-email-wangyunjian@huawei.com>
2025-12-18 10:57 ` |SUCCESS| pw159355 [PATCH v2] net/mlx5: fix memoy leak after device spawn failure checkpatch
2025-12-18 12:01 ` qemudev
2025-12-18 12:03 ` |FAILURE| " 0-day Robot
2025-12-18 12:06 ` |SUCCESS| " qemudev
2025-12-18 14:33 ` |SUCCESS| pw159355 [PATCH] [v2] net/mlx5: fix memoy leak after devic dpdklab
2025-12-18 14:39 ` |PENDING| " dpdklab
2025-12-18 14:40 ` dpdklab [this message]
2025-12-18 14:42 ` |SUCCESS| " dpdklab
2025-12-18 14:53 ` dpdklab
2025-12-18 14:54 ` dpdklab
2025-12-18 14:55 ` dpdklab
2025-12-18 14:55 ` dpdklab
2025-12-18 15:11 ` dpdklab
2025-12-18 15:13 ` dpdklab
2025-12-18 15:14 ` |PENDING| " dpdklab
2025-12-18 15:36 ` |SUCCESS| " dpdklab
2025-12-18 15:57 ` dpdklab
2025-12-18 15:57 ` dpdklab
2025-12-18 15:57 ` dpdklab
2025-12-18 15:58 ` dpdklab
2025-12-18 15:58 ` dpdklab
2025-12-18 16:17 ` dpdklab
2025-12-18 17:59 ` dpdklab
2025-12-19 1:23 ` dpdklab
2025-12-21 2:56 ` 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=6944124c.050a0220.1fa242.d60cSMTPIN_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).