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 17:03:43 -0700 (PDT)	[thread overview]
Message-ID: <685f315f.050a0220.3d7fbd.e00cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250627163729.50460-6-bingz@nvidia.com>

Test-Label: iol-unit-arm64-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: Generic-Unit-Test-DPDK#350494

Test environment and result as below:

+------------------------------+----------------+--------------+---------------------------+------------------------------+
|         Environment          | dpdk_unit_test | lpm_autotest | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest |
+==============================+================+==============+===========================+==============================+
| Debian GNU/Linux 12          | PEND           | SKIPPED      | SKIPPED                   | SKIPPED                      |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| Fedora Linux 40              | PEND           | SKIPPED      | SKIPPED                   | SKIPPED                      |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| CentOS Stream 9              | PEND           | SKIPPED      | SKIPPED                   | SKIPPED                      |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| Fedora Linux 41              | WARN           | SKIPPED      | SKIPPED                   | SKIPPED                      |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| CentOS Stream 10             | PEND           | SKIPPED      | SKIPPED                   | SKIPPED                      |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| Red Hat Enterprise Linux 9.5 | PEND           | SKIPPED      | SKIPPED                   | SKIPPED                      |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| Ubuntu 24.04                 | PEND           | SKIPPED      | SKIPPED                   | SKIPPED                      |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| Ubuntu 20.04                 | PEND           | PASS         | SKIPPED                   | SKIPPED                      |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| Ubuntu 22.04                 | PASS           | SKIPPED      | SKIPPED                   | SKIPPED                      |
+------------------------------+----------------+--------------+---------------------------+------------------------------+
| Debian 12 (arm)              | SKIPPED        | SKIPPED      | PEND                      | PEND                         |
+------------------------------+----------------+--------------+---------------------------+------------------------------+

==== 20 line log output for Fedora Linux 41 (dpdk_unit_test): ====
../drivers/net/mlx5/mlx5_devx.c:1671:48: error: 'act_cq_len' may be used uninitialized [-Werror=maybe-uninitialized]
1671 |                 priv->consec_tx_mem.cq_cur_off += act_cq_len;
|                                                ^~
../drivers/net/mlx5/mlx5_devx.c:1555:18: note: 'act_cq_len' was declared here
1555 |         uint32_t act_cq_len, alignment;
|                  ^~~~~~~~~~
In function 'mlx5_txq_create_devx_sq_resources',
inlined from 'mlx5_txq_devx_obj_new' at ../drivers/net/mlx5/mlx5_devx.c:1626:8:
../drivers/net/mlx5/mlx5_devx.c:1513:48: error: 'act_sq_len' may be used uninitialized [-Werror=maybe-uninitialized]
1513 |                 priv->consec_tx_mem.sq_cur_off += act_sq_len;
|                                                ^~
../drivers/net/mlx5/mlx5_devx.c: In function 'mlx5_txq_devx_obj_new':
../drivers/net/mlx5/mlx5_devx.c:1497:18: note: 'act_sq_len' was declared here
1497 |         uint32_t act_sq_len, alignment;
|                  ^~~~~~~~~~
cc1: all warnings being treated as errors
[2114/3719] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_ethdev.c.o
[2115/3719] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5.c.o
[2116/3719] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow.c.o
ninja: build stopped: subcommand failed.
==== End log output ====

Debian GNU/Linux 12
	Kernel: 5.4
	Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0

Fedora Linux 40
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)

CentOS Stream 9
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-7)

Fedora Linux 41
	Kernel: 5.4
	Compiler: clang gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)

CentOS Stream 10
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-8)

Red Hat Enterprise Linux 9.5
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)

Ubuntu 24.04
	Kernel: 5.4
	Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

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

Ubuntu 22.04
	Kernel: 5.4
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Debian 12 (arm)
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

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-28  0:03 UTC|newest]

Thread overview: 32+ 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
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 ` dpdklab [this message]
2025-06-28  0:32 ` |FAILURE| " dpdklab
2025-06-28  1:25 ` |WARNING| " dpdklab
2025-06-28  2:52 ` |FAILURE| " 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=685f315f.050a0220.3d7fbd.e00cSMTPIN_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).