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: |PENDING| pw156321-156339 [PATCH] [19/19] drivers: fix Klocwork issu
Date: Mon, 01 Sep 2025 01:18:48 -0700 (PDT)	[thread overview]
Message-ID: <68b556e8.050a0220.2f2a2.6987SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250901073036.1381560-19-ndabilpuram@marvell.com>

Test-Label: iol-compile-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/156339

_Testing pending_

Submitter: Nithin Dabilpuram <ndabilpuram@marvell.com>
Date: Monday, September 01 2025 07:30:35 
DPDK git baseline: Repo:dpdk-next-net-mrvl
  Branch: master
  CommitID:e3183a6edafdc41bfd71de1517f9e9ec85eb1276

156321-156339 --> testing pending

Upstream job id: Generic-DPDK-Compile-Meson#421766

Test environment and result as below:

+------------------------------+--------------------+
|         Environment          | dpdk_meson_compile |
+==============================+====================+
| Ubuntu 22.04                 | PEND               |
+------------------------------+--------------------+
| Red Hat Enterprise Linux 9.5 | PEND               |
+------------------------------+--------------------+
| Ubuntu 20.04                 | PASS               |
+------------------------------+--------------------+
| Debian GNU/Linux 12          | PEND               |
+------------------------------+--------------------+
| Fedora Linux 42              | PEND               |
+------------------------------+--------------------+
| CentOS Stream 10             | PEND               |
+------------------------------+--------------------+
| Ubuntu 24.04                 | PEND               |
+------------------------------+--------------------+
| CentOS Stream 9              | PEND               |
+------------------------------+--------------------+


Ubuntu 22.04
	Kernel: 5.4
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Red Hat Enterprise Linux 9.5
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)

Ubuntu 20.04
	Kernel: 5.15
	Compiler: aarch64-linux-gnu-gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Debian GNU/Linux 12
	Kernel: 5.4
	Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0

Fedora Linux 42
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 15.2.1 20250808 (Red Hat 15.2.1-1)

CentOS Stream 10
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-8)

Ubuntu 24.04
	Kernel: 5.4
	Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

CentOS Stream 9
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11)

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-09-01  8:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250901073036.1381560-19-ndabilpuram@marvell.com>
2025-09-01  7:00 ` |SUCCESS| pw156321-156339 [PATCH 19/19] drivers: fix Klocwork issues qemudev
2025-09-01  7:05 ` qemudev
2025-09-01  7:32 ` |SUCCESS| pw156339 " checkpatch
2025-09-01  8:00 ` |PENDING| pw156321-156339 [PATCH] [19/19] drivers: fix Klocwork issu dpdklab
2025-09-01  8:02 ` dpdklab
2025-09-01  8:04 ` |SUCCESS| " dpdklab
2025-09-01  8:07 ` dpdklab
2025-09-01  8:18 ` dpdklab [this message]
2025-09-01  8:22 ` dpdklab
2025-09-01  8:24 ` dpdklab
2025-09-01  8:24 ` dpdklab
2025-09-01  8:26 ` |WARNING| " dpdklab
2025-09-01  8:26 ` |SUCCESS| pw156339 [PATCH 19/19] drivers: fix Klocwork issues 0-day Robot
2025-09-01  8:31 ` |SUCCESS| pw156321-156339 [PATCH] [19/19] drivers: fix Klocwork issu dpdklab
2025-09-01  8:33 ` dpdklab
2025-09-01  8:36 ` |PENDING| " dpdklab
2025-09-01  8:43 ` |SUCCESS| " dpdklab
2025-09-01  8:46 ` |WARNING| " dpdklab
2025-09-01  8:46 ` |SUCCESS| " dpdklab
2025-09-01 13:14 ` dpdklab
2025-09-01 14:28 ` dpdklab
2025-09-03  0:57 ` 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=68b556e8.050a0220.2f2a2.6987SMTPIN_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).