From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw158283 [PATCH] pmdinfogen: fix warning with python 3.14
Date: Wed, 29 Oct 2025 13:10:49 -0700 (PDT) [thread overview]
Message-ID: <690274c9.170a0220.60073.31c4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251029164616.76233-2-rjarry@redhat.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/158283
_Testing PASS_
Submitter: Robin Jarry <rjarry@redhat.com>
Date: Wednesday, October 29 2025 16:46:17
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:39b54f2dcf44ad1f91eabc7080cd5dea763607fd
158283 --> testing pass
Upstream job id: Windows-Compile-DPDK-Native#31994
Test environment and result as below:
+---------------------+--------------------+-------------------+-------------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_msvc_compile | dpdk_llvm_clang_compile | dpdk_mingw64_compile |
+=====================+====================+===================+=========================+======================+
| Ubuntu 20.04 | PASS | SKIPPED | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+-------------------------+----------------------+
| FreeBSD 14.2 | PASS | SKIPPED | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+-------------------------+----------------------+
| Windows Server 2022 | SKIPPED | PASS | PASS | PASS |
+---------------------+--------------------+-------------------+-------------------------+----------------------+
Ubuntu 20.04
Kernel: 4.19
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
FreeBSD 14.2
Kernel: 14.2-RELEASE
Compiler: clang 18.1.6
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/34420/
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-10-29 20:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251029164616.76233-2-rjarry@redhat.com>
2025-10-29 16:11 ` |SUCCESS| pw158283 [PATCH dpdk] " qemudev
2025-10-29 16:16 ` qemudev
2025-10-29 16:47 ` checkpatch
2025-10-29 17:12 ` |PENDING| pw158283 [PATCH] " dpdklab
2025-10-29 17:15 ` |SUCCESS| " dpdklab
2025-10-29 17:18 ` dpdklab
2025-10-29 17:20 ` dpdklab
2025-10-29 17:25 ` |PENDING| " dpdklab
2025-10-29 17:31 ` |WARNING| " dpdklab
2025-10-29 17:48 ` |SUCCESS| " dpdklab
2025-10-29 18:00 ` dpdklab
2025-10-29 18:01 ` |PENDING| " dpdklab
2025-10-29 18:08 ` |SUCCESS| " dpdklab
2025-10-29 18:08 ` |PENDING| " dpdklab
2025-10-29 18:08 ` |SUCCESS| " dpdklab
2025-10-29 18:25 ` dpdklab
2025-10-29 19:07 ` |SUCCESS| pw158283 [PATCH dpdk] " 0-day Robot
2025-10-29 19:08 ` 0-day Robot
2025-10-29 19:14 ` |SUCCESS| pw158283 [PATCH] " dpdklab
2025-10-29 19:25 ` |WARNING| " dpdklab
2025-10-29 19:33 ` |SUCCESS| " dpdklab
2025-10-29 19:47 ` dpdklab
2025-10-29 19:57 ` dpdklab
2025-10-29 20:05 ` dpdklab
2025-10-29 20:09 ` dpdklab
2025-10-29 20:10 ` dpdklab [this message]
2025-10-29 23:00 ` |PENDING| " dpdklab
2025-10-29 23:29 ` |WARNING| " dpdklab
2025-10-30 3:42 ` |SUCCESS| " 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=690274c9.170a0220.60073.31c4SMTPIN_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).