From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Stephen Hemminger <stephen@networkplumber.org>
Subject: |SUCCESS| pw156569 [PATCH] [v1] net/zxdh: add support compiling on r
Date: Wed, 10 Sep 2025 20:36:46 -0700 (PDT) [thread overview]
Message-ID: <68c243ce.d40a0220.1e8098.1ea6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250911023211.3576860-1-wang.junlong1@zte.com.cn>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/156569
_Testing PASS_
Submitter: Junlong Wang <wang.junlong1@zte.com.cn>
Date: Thursday, September 11 2025 02:32:11
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:96eebfe1330def4b2565fa09a299c2861d7d0d61
156569 --> testing pass
Upstream job id: Windows-Compile-DPDK-Native#30898
Test environment and result as below:
+---------------------+--------------------+-------------------------+-------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_llvm_clang_compile | dpdk_msvc_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/34054/
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-09-11 3:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250911023211.3576860-1-wang.junlong1@zte.com.cn>
2025-09-11 2:23 ` |SUCCESS| pw156569 [PATCH v1] net/zxdh: add support compiling on riscv-64 systems qemudev
2025-09-11 2:29 ` qemudev
2025-09-11 2:42 ` checkpatch
2025-09-11 3:07 ` |PENDING| pw156569 [PATCH] [v1] net/zxdh: add support compiling on r dpdklab
2025-09-11 3:11 ` dpdklab
2025-09-11 3:16 ` |SUCCESS| " dpdklab
2025-09-11 3:19 ` |PENDING| " dpdklab
2025-09-11 3:30 ` dpdklab
2025-09-11 3:31 ` |SUCCESS| " dpdklab
2025-09-11 3:33 ` dpdklab
2025-09-11 3:33 ` dpdklab
2025-09-11 3:35 ` dpdklab
2025-09-11 3:35 ` dpdklab
2025-09-11 3:36 ` dpdklab [this message]
2025-09-11 3:40 ` dpdklab
2025-09-11 3:47 ` |SUCCESS| pw156569 [PATCH v1] net/zxdh: add support compiling on riscv-64 systems 0-day Robot
2025-09-11 3:47 ` 0-day Robot
2025-09-11 3:50 ` |SUCCESS| pw156569 [PATCH] [v1] net/zxdh: add support compiling on r dpdklab
2025-09-11 7:33 ` |PENDING| " dpdklab
2025-09-11 7:57 ` |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=68c243ce.d40a0220.1e8098.1ea6SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=stephen@networkplumber.org \
--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).