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| pw154799-154801 [PATCH] [v3,5/5] net/mlx5: use consecutive
Date: Fri, 27 Jun 2025 13:00:15 -0700 (PDT)	[thread overview]
Message-ID: <685ef84f.250a0220.283f3b.7097SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250627163729.50460-6-bingz@nvidia.com>

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

_Testing issues_

Submitter: Bing Zhao <bingz@nvidia.com>
Date: Friday, June 27 2025 16:37:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5c0c1a13c34aa57c6e18f9ba852a9b5807c58b72

154799-154801 --> testing issues

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

Test environment and result as below:

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

==== 20 line log output for Ubuntu 20.04 (dpdk_meson_compile): ====
[1953/3522] Generating rte_common_mlx5.sym_chk with a custom command (wrapped by meson to capture output)
[1954/3522] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_mac.c.o
[1955/3522] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rss.c.o
[1956/3522] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_aso.c.o
[1957/3522] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5.c.o
[1958/3522] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_nta_rss.c.o
[1959/3522] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rxmode.c.o
[1960/3522] Generating rte_net_idpf.sym_chk with a custom command (wrapped by meson to capture output)
[1961/3522] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rxtx.c.o
[1962/3522] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_stats.c.o
[1963/3522] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_meter.c.o
[1964/3522] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx.c.o
[1965/3522] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_trigger.c.o
[1966/3522] Generating rte_common_sfc_efx.sym_chk with a custom command (wrapped by meson to capture output)
[1967/3522] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rxq.c.o
[1968/3522] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rx.c.o
[1969/3522] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow.c.o
[1970/3522] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[1971/3522] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_dv.c.o
ninja: build stopped: subcommand failed.
==== End log output ====

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

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

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-27 20:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250627163729.50460-6-bingz@nvidia.com>
2025-06-27 16:05 ` |SUCCESS| pw154799-154801 [PATCH v3 5/5] net/mlx5: use consecutive memory for Tx queue creation qemudev
2025-06-27 16:10 ` qemudev
2025-06-27 16:37 ` |SUCCESS| pw154801 " checkpatch
2025-06-27 18:07 ` |FAILURE| " 0-day Robot
2025-06-27 19:04 ` |SUCCESS| pw154799-154801 [PATCH] [v3,5/5] net/mlx5: use consecutive dpdklab
2025-06-27 19:08 ` dpdklab
2025-06-27 19:23 ` |FAILURE| " dpdklab
2025-06-27 19:27 ` dpdklab
2025-06-27 20:00 ` dpdklab [this message]
2025-06-27 20:04 ` |PENDING| " dpdklab
2025-06-27 20:49 ` |SUCCESS| " dpdklab
2025-06-27 20:50 ` |FAILURE| " dpdklab
2025-06-27 21:01 ` |SUCCESS| " dpdklab
2025-06-27 21:36 ` dpdklab
2025-06-27 22:00 ` |FAILURE| " dpdklab
2025-06-27 22:42 ` dpdklab
2025-06-27 23:00 ` dpdklab
2025-06-27 23:01 ` dpdklab
2025-06-27 23:04 ` dpdklab
2025-06-27 23:06 ` dpdklab
2025-06-27 23:08 ` dpdklab
2025-06-27 23:12 ` |WARNING| " dpdklab
2025-06-27 23:16 ` |PENDING| " dpdklab
2025-06-27 23:32 ` |FAILURE| " dpdklab
2025-06-27 23:53 ` |SUCCESS| " dpdklab
2025-06-27 23:54 ` dpdklab
2025-06-27 23:55 ` dpdklab
2025-06-27 23:56 ` |PENDING| " dpdklab
2025-06-28  0:03 ` |FAILURE| " dpdklab
2025-06-28  0:32 ` 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=685ef84f.250a0220.283f3b.7097SMTPIN_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).