From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw146828 [PATCH] [v3] net/mlx5: fix potential memory leak
Date: Sat, 26 Oct 2024 09:49:07 -0700 (PDT) [thread overview]
Message-ID: <671d1d83.170a0220.2131c7.a03eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241023062216.967742-1-shunh@nvidia.com>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/146828
_Testing PASS_
Submitter: Shun Hao <shunh@nvidia.com>
Date: Wednesday, October 23 2024 06:22:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c4f029602e46450a0c51953c4607e53488244071
146828 --> testing pass
Upstream job id: Generic-DPDK-Compile-Meson#323383
Test environment and result as below:
+------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+------------------------------------+--------------------+
| Debian 12 with MUSDK | PASS |
+------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+------------------------------------+--------------------+
| Fedora 38 (ARM Clang) | PASS |
+------------------------------------+--------------------+
| Fedora 40 (ARM Clang) | PASS |
+------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+------------------------------------+--------------------+
| Fedora 40 (ARM) | PASS |
+------------------------------------+--------------------+
| Ubuntu 22.04 (ARM) | PASS |
+------------------------------------+--------------------+
| Fedora 39 (ARM Clang) | PASS |
+------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+------------------------------------+--------------------+
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: Depends on container host
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Debian 12 with MUSDK
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1 20240316 (Red Hat 13.2.1-7)
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6 (Fedora 16.0.6-4.fc38)
Fedora 40 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)
Ubuntu 20.04 (ARM)
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Fedora 40 (ARM)
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)
Ubuntu 22.04 (ARM)
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Fedora 39 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)
CentOS Stream 9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31614/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2024-10-26 16:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241023062216.967742-1-shunh@nvidia.com>
2024-10-23 6:03 ` |SUCCESS| pw146828 [PATCH v3] net/mlx5: fix potential memory leak in meter qemudev
2024-10-23 6:07 ` qemudev
2024-10-23 6:23 ` |WARNING| " checkpatch
2024-10-23 7:26 ` |SUCCESS| " 0-day Robot
2024-10-23 12:22 ` |SUCCESS| pw146828 [PATCH] [v3] net/mlx5: fix potential memory leak dpdklab
2024-10-23 17:50 ` dpdklab
2024-10-23 18:02 ` dpdklab
2024-10-23 19:19 ` dpdklab
2024-10-23 21:13 ` dpdklab
2024-10-24 7:07 ` dpdklab
2024-10-24 7:43 ` dpdklab
2024-10-25 1:34 ` |PENDING| " dpdklab
2024-10-25 5:44 ` |SUCCESS| " dpdklab
2024-10-25 6:06 ` dpdklab
2024-10-26 1:40 ` |PENDING| " dpdklab
2024-10-26 1:45 ` |SUCCESS| " dpdklab
2024-10-26 16:49 ` dpdklab [this message]
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=671d1d83.170a0220.2131c7.a03eSMTPIN_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).