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| pw154604-154605 [PATCH] [v7,2/2] node: use node mbuf dynfi
Date: Thu, 19 Jun 2025 12:13:43 -0700 (PDT)	[thread overview]
Message-ID: <68546167.050a0220.373d70.0272SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250619154501.3869031-3-nsaxena@marvell.com>

Test-Label: iol-unit-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/154605

_Testing pending_

Submitter: Nitin Saxena <nsaxena@marvell.com>
Date: Thursday, June 19 2025 15:44:50 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6890ee7ba76e92745d6c61b3b6b9d757ebaaa89d

154604-154605 --> testing pending

Upstream job id: Generic-Unit-Test-DPDK#347870

Test environment and result as below:

+-------------------------------+----------------+
|          Environment          | dpdk_unit_test |
+===============================+================+
| CentOS Stream 9               | PASS           |
+-------------------------------+----------------+
| CentOS Stream 10              | PEND           |
+-------------------------------+----------------+
| Fedora Linux 40               | PEND           |
+-------------------------------+----------------+
| Debian GNU/Linux 12           | PEND           |
+-------------------------------+----------------+
| Fedora Linux 41               | PEND           |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 8.10 | PEND           |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 9.5  | PEND           |
+-------------------------------+----------------+
| Ubuntu 20.04                  | PEND           |
+-------------------------------+----------------+
| Ubuntu 22.04                  | PEND           |
+-------------------------------+----------------+
| Ubuntu 24.04                  | PEND           |
+-------------------------------+----------------+
| Windows Server 2022           | PEND           |
+-------------------------------+----------------+


CentOS Stream 9
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-7)

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

Fedora Linux 40
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)

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

Fedora Linux 41
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)

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.5
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)

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

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

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

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/33465/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-06-19 19:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250619154501.3869031-3-nsaxena@marvell.com>
2025-06-19 15:17 ` |SUCCESS| pw154604-154605 [PATCH v7 2/2] node: use node mbuf dynfield in ip4 nodes qemudev
2025-06-19 15:21 ` qemudev
2025-06-19 15:45 ` |SUCCESS| pw154605 " checkpatch
2025-06-19 17:06 ` 0-day Robot
2025-06-19 17:44 ` |SUCCESS| pw154604-154605 [PATCH] [v7,2/2] node: use node mbuf dynfi dpdklab
2025-06-19 17:55 ` dpdklab
2025-06-19 18:03 ` dpdklab
2025-06-19 18:06 ` |PENDING| " dpdklab
2025-06-19 18:11 ` |SUCCESS| " dpdklab
2025-06-19 18:58 ` |PENDING| " dpdklab
2025-06-19 19:03 ` |SUCCESS| " dpdklab
2025-06-19 19:04 ` dpdklab
2025-06-19 19:10 ` |PENDING| " dpdklab
2025-06-19 19:13 ` dpdklab [this message]
2025-06-19 19:27 ` |SUCCESS| " dpdklab
2025-06-19 19:39 ` dpdklab
2025-06-19 19:58 ` dpdklab
2025-06-19 20:13 ` |WARNING| " dpdklab
2025-06-19 20:13 ` dpdklab
2025-06-19 20:16 ` dpdklab
2025-06-19 20:30 ` dpdklab
2025-06-19 20:33 ` dpdklab
2025-06-19 22:18 ` |SUCCESS| " dpdklab
2025-06-19 23:11 ` dpdklab
2025-06-19 23:12 ` dpdklab
2025-06-20  0:26 ` 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=68546167.050a0220.373d70.0272SMTPIN_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).