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| pw141118 [PATCH] [v3] net/mana: fix uninitialized scalar v
Date: Wed, 12 Jun 2024 18:35:03 -0700 (PDT)	[thread overview]
Message-ID: <666a4cc7.170a0220.a06e3.05e9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240612182332.804748-1-mahmoudmatook.mm@gmail.com>

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

_Testing PASS_

Submitter: Mahmoud Maatuq <mahmoudmatook.mm@gmail.com>
Date: Wednesday, June 12 2024 18:23:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:491f416ae7a87dc0526f3472c722ac48f2163521

141118 --> testing pass

Test environment and result as below:

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


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

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

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

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

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

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

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

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

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

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-13  1:36 UTC|newest]

Thread overview: 105+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240612182332.804748-1-mahmoudmatook.mm@gmail.com>
2024-06-12 17:59 ` |SUCCESS| pw141118 [PATCH v3] net/mana: fix uninitialized scalar variable qemudev
2024-06-12 18:03 ` qemudev
2024-06-12 18:25 ` checkpatch
2024-06-12 19:25 ` 0-day Robot
2024-06-13  0:04 ` |SUCCESS| pw141118 [PATCH] [v3] net/mana: fix uninitialized scalar v dpdklab
2024-06-13  1:06 ` dpdklab
2024-06-13  1:32 ` dpdklab
2024-06-13  1:32 ` dpdklab
2024-06-13  1:32 ` dpdklab
2024-06-13  1:32 ` dpdklab
2024-06-13  1:34 ` dpdklab
2024-06-13  1:34 ` dpdklab
2024-06-13  1:34 ` dpdklab
2024-06-13  1:34 ` dpdklab
2024-06-13  1:34 ` dpdklab
2024-06-13  1:35 ` dpdklab [this message]
2024-06-13  1:35 ` dpdklab
2024-06-13  1:35 ` dpdklab
2024-06-13  1:35 ` dpdklab
2024-06-13  1:35 ` dpdklab
2024-06-13  1:35 ` dpdklab
2024-06-13  1:36 ` dpdklab
2024-06-13  1:36 ` dpdklab
2024-06-13  1:36 ` dpdklab
2024-06-13  1:36 ` dpdklab
2024-06-13  1:36 ` dpdklab
2024-06-13  1:37 ` dpdklab
2024-06-13  1:37 ` dpdklab
2024-06-13  1:37 ` dpdklab
2024-06-13  1:37 ` dpdklab
2024-06-13  1:37 ` dpdklab
2024-06-13  1:37 ` dpdklab
2024-06-13  1:37 ` dpdklab
2024-06-13  1:37 ` dpdklab
2024-06-13  1:37 ` dpdklab
2024-06-13  1:38 ` dpdklab
2024-06-13  1:38 ` dpdklab
2024-06-13  1:38 ` dpdklab
2024-06-13  1:38 ` dpdklab
2024-06-13  1:38 ` dpdklab
2024-06-13  1:38 ` dpdklab
2024-06-13  1:38 ` dpdklab
2024-06-13  1:38 ` dpdklab
2024-06-13  1:38 ` dpdklab
2024-06-13  1:38 ` dpdklab
2024-06-13  1:39 ` dpdklab
2024-06-13  1:39 ` dpdklab
2024-06-13  1:39 ` dpdklab
2024-06-13  1:39 ` dpdklab
2024-06-13  1:39 ` dpdklab
2024-06-13  1:39 ` dpdklab
2024-06-13  1:39 ` dpdklab
2024-06-13  1:39 ` dpdklab
2024-06-13  1:40 ` dpdklab
2024-06-13  1:40 ` dpdklab
2024-06-13  1:40 ` dpdklab
2024-06-13  1:40 ` dpdklab
2024-06-13  1:40 ` dpdklab
2024-06-13  1:40 ` dpdklab
2024-06-13  1:40 ` dpdklab
2024-06-13  1:40 ` dpdklab
2024-06-13  1:41 ` dpdklab
2024-06-13  1:41 ` dpdklab
2024-06-13  1:41 ` dpdklab
2024-06-13  1:42 ` dpdklab
2024-06-13  1:42 ` dpdklab
2024-06-13  1:42 ` dpdklab
2024-06-13  1:42 ` dpdklab
2024-06-13  1:42 ` dpdklab
2024-06-13  1:42 ` dpdklab
2024-06-13  1:42 ` dpdklab
2024-06-13  1:43 ` dpdklab
2024-06-13  1:43 ` dpdklab
2024-06-13  1:43 ` dpdklab
2024-06-13  1:43 ` dpdklab
2024-06-13  1:43 ` dpdklab
2024-06-13  1:44 ` dpdklab
2024-06-13  1:44 ` dpdklab
2024-06-13  1:44 ` dpdklab
2024-06-13  1:44 ` dpdklab
2024-06-13  1:44 ` dpdklab
2024-06-13  1:44 ` dpdklab
2024-06-13  1:44 ` dpdklab
2024-06-13  1:45 ` dpdklab
2024-06-13  1:45 ` dpdklab
2024-06-13  1:45 ` dpdklab
2024-06-13  1:45 ` dpdklab
2024-06-13  1:47 ` dpdklab
2024-06-13  1:48 ` dpdklab
2024-06-13  1:49 ` dpdklab
2024-06-13  1:52 ` dpdklab
2024-06-13  1:52 ` dpdklab
2024-06-13  1:52 ` dpdklab
2024-06-13  1:53 ` dpdklab
2024-06-13  1:53 ` dpdklab
2024-06-13  1:55 ` dpdklab
2024-06-13  1:56 ` dpdklab
2024-06-13  1:56 ` dpdklab
2024-06-13  1:56 ` dpdklab
2024-06-13  1:59 ` dpdklab
2024-06-13  1:59 ` dpdklab
2024-06-13  2:02 ` dpdklab
2024-06-13  3:27 ` dpdklab
2024-06-13  4:06 ` dpdklab
2024-06-13  4:51 ` 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=666a4cc7.170a0220.a06e3.05e9SMTPIN_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).