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| pw141488 [PATCH] net/mlx5: fix memleak for resource object
Date: Sun, 23 Jun 2024 04:39:58 -0700 (PDT)	[thread overview]
Message-ID: <6678098e.170a0220.619c6.7f8eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240623103539.1690600-1-mahmoudmatook.mm@gmail.com>

Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141488

_Testing PASS_

Submitter: Mahmoud Maatuq <mahmoudmatook.mm@gmail.com>
Date: Sunday, June 23 2024 10:35:39 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c1cdfbcc339c2c951bff95854983a8773d9e5b8e

141488 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| Fedora 40        | PASS     |
+------------------+----------+
| Fedora 39        | PASS     |
+------------------+----------+
| Fedora 38        | PASS     |
+------------------+----------+
| CentOS Stream 9  | PASS     |
+------------------+----------+
| RHEL9            | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| Debian Bullseye  | PASS     |
+------------------+----------+
| Ubuntu 24.04     | PASS     |
+------------------+----------+
| CentOS Stream 8  | PASS     |
+------------------+----------+
| RHEL8            | PASS     |
+------------------+----------+


Fedora 40
	Kernel: Depends on container host
	Compiler: clang 18.1.6

Fedora 39
	Kernel: Depends on container host
	Compiler: clang 17.0.6

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.6

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

Ubuntu 24.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-23 11:40 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240623103539.1690600-1-mahmoudmatook.mm@gmail.com>
2024-06-23 10:09 ` qemudev
2024-06-23 10:14 ` qemudev
2024-06-23 10:37 ` checkpatch
2024-06-23 11:24 ` 0-day Robot
2024-06-23 11:25 ` dpdklab
2024-06-23 11:25 ` dpdklab
2024-06-23 11:26 ` dpdklab
2024-06-23 11:26 ` dpdklab
2024-06-23 11:26 ` dpdklab
2024-06-23 11:26 ` dpdklab
2024-06-23 11:26 ` dpdklab
2024-06-23 11:26 ` dpdklab
2024-06-23 11:27 ` dpdklab
2024-06-23 11:27 ` dpdklab
2024-06-23 11:27 ` dpdklab
2024-06-23 11:27 ` dpdklab
2024-06-23 11:27 ` dpdklab
2024-06-23 11:27 ` dpdklab
2024-06-23 11:28 ` dpdklab
2024-06-23 11:28 ` dpdklab
2024-06-23 11:28 ` dpdklab
2024-06-23 11:28 ` dpdklab
2024-06-23 11:28 ` dpdklab
2024-06-23 11:29 ` dpdklab
2024-06-23 11:29 ` dpdklab
2024-06-23 11:29 ` dpdklab
2024-06-23 11:30 ` dpdklab
2024-06-23 11:30 ` dpdklab
2024-06-23 11:31 ` dpdklab
2024-06-23 11:32 ` dpdklab
2024-06-23 11:32 ` dpdklab
2024-06-23 11:32 ` dpdklab
2024-06-23 11:33 ` dpdklab
2024-06-23 11:34 ` dpdklab
2024-06-23 11:35 ` dpdklab
2024-06-23 11:35 ` dpdklab
2024-06-23 11:36 ` dpdklab
2024-06-23 11:37 ` dpdklab
2024-06-23 11:39 ` dpdklab
2024-06-23 11:39 ` dpdklab [this message]
2024-06-23 11:40 ` dpdklab
2024-06-23 11:40 ` dpdklab
2024-06-23 11:40 ` dpdklab
2024-06-23 11:41 ` dpdklab
2024-06-23 11:42 ` dpdklab
2024-06-23 11:42 ` dpdklab
2024-06-23 11:43 ` dpdklab
2024-06-23 11:43 ` dpdklab
2024-06-23 11:44 ` dpdklab
2024-06-23 11:50 ` dpdklab
2024-06-23 11:54 ` dpdklab
2024-06-23 11:56 ` dpdklab
2024-06-23 11:58 ` dpdklab
2024-06-23 12:02 ` dpdklab
2024-06-23 12:03 ` dpdklab
2024-06-23 12:04 ` dpdklab
2024-06-23 12:05 ` dpdklab
2024-06-23 12:06 ` dpdklab
2024-06-23 12:07 ` dpdklab
2024-06-23 12:09 ` dpdklab
2024-06-23 12:10 ` dpdklab
2024-06-23 12:10 ` dpdklab
2024-06-23 12:11 ` dpdklab
2024-06-23 12:12 ` dpdklab
2024-06-23 12:13 ` dpdklab
2024-06-23 12:14 ` dpdklab
2024-06-23 12:14 ` dpdklab
2024-06-23 12:15 ` dpdklab
2024-06-23 12:17 ` dpdklab
2024-06-23 12:18 ` dpdklab
2024-06-23 12:18 ` dpdklab
2024-06-23 12:19 ` dpdklab
2024-06-23 12:22 ` dpdklab
2024-06-23 12:22 ` dpdklab
2024-06-23 12:23 ` dpdklab
2024-06-23 12:23 ` dpdklab
2024-06-23 12:25 ` dpdklab
2024-06-23 12:26 ` dpdklab
2024-06-23 12:27 ` dpdklab
2024-06-23 12:27 ` dpdklab
2024-06-23 12:29 ` dpdklab
2024-06-23 12:29 ` dpdklab
2024-06-23 12:31 ` dpdklab
2024-06-23 12:33 ` dpdklab
2024-06-23 12:35 ` dpdklab
2024-06-23 12:35 ` dpdklab
2024-06-23 12:36 ` dpdklab
2024-06-23 12:37 ` dpdklab
2024-06-23 12:37 ` dpdklab
2024-06-23 12:38 ` dpdklab
2024-06-23 12:41 ` dpdklab
2024-06-23 12:42 ` dpdklab
2024-06-23 12:42 ` dpdklab
2024-06-23 12:42 ` dpdklab
2024-06-23 12:43 ` dpdklab
2024-06-23 12:46 ` dpdklab
2024-06-23 12:48 ` dpdklab
2024-06-23 12:49 ` dpdklab
2024-06-23 12:50 ` dpdklab
2024-06-23 12:50 ` dpdklab
2024-06-23 12:51 ` dpdklab
2024-06-23 12:52 ` dpdklab
2024-06-23 12:58 ` dpdklab
2024-06-23 13:01 ` dpdklab
2024-06-23 13:02 ` dpdklab
2024-06-23 13:04 ` dpdklab
2024-06-23 13:05 ` dpdklab
2024-06-23 13:06 ` dpdklab
2024-06-23 13:06 ` dpdklab
2024-06-23 13:12 ` dpdklab
2024-06-23 13:15 ` dpdklab
2024-06-23 13:18 ` dpdklab
2024-06-23 13:23 ` dpdklab
2024-06-23 13:33 ` 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=6678098e.170a0220.619c6.7f8eSMTPIN_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).