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, Bing Zhao <bingz@nvidia.com>
Subject: |FAILURE| pw158844-158845 [PATCH] [2/2] net/mlx5: use private struct
Date: Sun, 16 Nov 2025 21:49:51 -0800 (PST)	[thread overview]
Message-ID: <691ab77f.050a0220.c5792.7876SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251117041537.8161-1-bingz@nvidia.com>

Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/158845

_Testing issues_

Submitter: Bing Zhao <bingz@nvidia.com>
Date: Monday, November 17 2025 04:15:37 
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: master
  CommitID:a3f565c41c73db0f965d62c72627980235d4d7e8

158844-158845 --> testing issues

Upstream job id: Windows-Compile-DPDK-Native#32464

Test environment and result as below:

+---------------------+-------------------------+--------------------+-------------------+
|     Environment     | dpdk_llvm_clang_compile | dpdk_meson_compile | dpdk_msvc_compile |
+=====================+=========================+====================+===================+
| Windows Server 2022 | PASS                    | SKIPPED            | PEND              |
+---------------------+-------------------------+--------------------+-------------------+
| FreeBSD 14.2        | SKIPPED                 | PEND               | SKIPPED           |
+---------------------+-------------------------+--------------------+-------------------+
| Ubuntu 20.04        | SKIPPED                 | FAIL               | SKIPPED           |
+---------------------+-------------------------+--------------------+-------------------+

==== 20 line log output for Ubuntu 20.04 (dpdk_meson_compile): ====
[2020/3604] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_verbs.c.o
[2021/3604] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_nta_sample.c.o
[2022/3604] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow.c.o
[2023/3604] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_linux_mlx5_mp_os.c.o
[2024/3604] Generating rte_common_sfc_efx.sym_chk with a custom command (wrapped by meson to capture output)
[2025/3604] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_linux_mlx5_vlan_os.c.o
[2026/3604] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_linux_mlx5_flow_os.c.o
[2027/3604] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_linux_mlx5_verbs.c.o
[2028/3604] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rxtx_vec.c.o
[2029/3604] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_hws_cnt.c.o
[2030/3604] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_linux_mlx5_ethdev_os.c.o
[2031/3604] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_linux_mlx5_os.c.o
[2032/3604] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_hws_mlx5dr_context.c.o
[2033/3604] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_mpw.c.o
[2034/3604] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[2035/3604] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_dv.c.o
[2036/3604] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_nompw.c.o
[2037/3604] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_empw.c.o
[2038/3604] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_txpp.c.o
ninja: build stopped: subcommand failed.
==== End log output ====

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521

FreeBSD 14.2
	Kernel: 14.2-RELEASE
	Compiler: clang 18.1.6

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-11-17  5:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251117041537.8161-1-bingz@nvidia.com>
2025-11-17  3:41 ` |SUCCESS| pw158844-158845 [PATCH 2/2] net/mlx5: use private structure for internal tag item qemudev
2025-11-17  3:46 ` qemudev
2025-11-17  4:16 ` |SUCCESS| pw158845 " checkpatch
2025-11-17  4:50 ` |FAILURE| " 0-day Robot
2025-11-17  5:48 ` |FAILURE| pw158844-158845 [PATCH] [2/2] net/mlx5: use private struct dpdklab
2025-11-17  5:49 ` dpdklab [this message]
2025-11-17  5:56 ` |SUCCESS| " dpdklab
2025-11-17  6:12 ` |FAILURE| " dpdklab
2025-11-17  6:48 ` |PENDING| " dpdklab
2025-11-17  6:49 ` dpdklab
2025-11-17  6:50 ` |FAILURE| " dpdklab
2025-11-17  6:51 ` |PENDING| " dpdklab
2025-11-17  7:57 ` |WARNING| " dpdklab
2025-11-17  8:25 ` |FAILURE| " dpdklab
2025-11-17  8:53 ` dpdklab
2025-11-17  8:54 ` dpdklab
2025-11-17  8:55 ` dpdklab
2025-11-17  8:56 ` dpdklab
2025-11-17  8:59 ` dpdklab
2025-11-17  8:59 ` dpdklab
2025-11-17  9:00 ` dpdklab
2025-11-17  9:01 ` dpdklab
2025-11-17  9:02 ` dpdklab
2025-11-17  9:03 ` dpdklab
2025-11-17  9:03 ` dpdklab
2025-11-17  9:09 ` 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=691ab77f.050a0220.c5792.7876SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bingz@nvidia.com \
    --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).