From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw156049-156051 [PATCH] [v5,3/3] mbuf: no need to reset al
Date: Thu, 21 Aug 2025 09:25:30 -0700 (PDT) [thread overview]
Message-ID: <68a7487a.170a0220.9e97.9213SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250821150250.16959-4-mb@smartsharesystems.com>
Test-Label: iol-unit-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/156051
_Testing pending_
Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Thursday, August 21 2025 15:02:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:38543d33bd47fc0ee21f59db80a8763620741879
156049-156051 --> testing pending
Upstream job id: Generic-Unit-Test-DPDK#364509
Test environment and result as below:
+-------------------------------+----------------+
| Environment | dpdk_unit_test |
+===============================+================+
| CentOS Stream 9 | PASS |
+-------------------------------+----------------+
| CentOS Stream 10 | PEND |
+-------------------------------+----------------+
| Debian GNU/Linux 12 | PEND |
+-------------------------------+----------------+
| Fedora Linux 40 | PEND |
+-------------------------------+----------------+
| Fedora Linux 41 | PEND |
+-------------------------------+----------------+
| Fedora Linux 42 | PEND |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 8.10 | PEND |
+-------------------------------+----------------+
| Ubuntu 20.04 | PEND |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 9.5 | PEND |
+-------------------------------+----------------+
| Ubuntu 22.04 | PEND |
+-------------------------------+----------------+
| Ubuntu 24.04 | 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)
Debian GNU/Linux 12
Kernel: 5.15
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
Fedora Linux 40
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora Linux 41
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
Fedora Linux 42
Kernel: 5.15
Compiler: gcc gcc (GCC) 15.1.1 20250521 (Red Hat 15.1.1-2)
Red Hat Enterprise Linux 8.10
Kernel: 5.15
Compiler: gcc gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-22)
Ubuntu 20.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Red Hat Enterprise Linux 9.5
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33927/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-08-21 16:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250821150250.16959-4-mb@smartsharesystems.com>
2025-08-21 14:29 ` |SUCCESS| pw156049-156051 [PATCH v5 3/3] mbuf: no need to reset all fields on reinitialized mbufs qemudev
2025-08-21 14:34 ` qemudev
2025-08-21 15:01 ` |SUCCESS| pw156051 " checkpatch
2025-08-21 16:06 ` |FAILURE| pw156049-156051 [PATCH] [v5,3/3] mbuf: no need to reset al dpdklab
2025-08-21 16:23 ` |PENDING| " dpdklab
2025-08-21 16:25 ` dpdklab [this message]
2025-08-21 16:25 ` |FAILURE| pw156051 [PATCH v5 3/3] mbuf: no need to reset all fields on reinitialized mbufs 0-day Robot
2025-08-21 16:27 ` |PENDING| pw156049-156051 [PATCH] [v5,3/3] mbuf: no need to reset al dpdklab
2025-08-21 16:29 ` |SUCCESS| " dpdklab
2025-08-21 16:45 ` dpdklab
2025-08-21 16:51 ` dpdklab
2025-08-21 17:02 ` dpdklab
2025-08-21 17:03 ` dpdklab
2025-08-21 17:04 ` dpdklab
2025-08-21 17:41 ` dpdklab
2025-08-21 17:50 ` dpdklab
2025-08-21 17:58 ` 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=68a7487a.170a0220.9e97.9213SMTPIN_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).