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
Subject: |WARNING| pw152093-152096 [PATCH] [V2,4/4] net/mlx5/hws: allow diffe
Date: Fri, 28 Feb 2025 09:18:37 -0800 (PST)	[thread overview]
Message-ID: <67c1efed.170a0220.ec8f6.9741SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250226083846.4023622-5-ophirmu@nvidia.com>

Test-Label: iol-unit-amd64-testing
Test-Status: WARNING
http://dpdk.org/patch/152096

_Testing issues_

Submitter: Ophir Munk <ophirmu@nvidia.com>
Date: Wednesday, February 26 2025 08:38:46 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fab31a03ba98e7457284df95dd9eef2223a4ccaa

152093-152096 --> testing issues

Upstream job id: Generic-Unit-Test-DPDK#320030

Test environment and result as below:

+-------------------+----------------+
|    Environment    | dpdk_unit_test |
+===================+================+
| Debian Bullseye   | WARN           |
+-------------------+----------------+
| CentOS Stream 10  | WARN           |
+-------------------+----------------+
| CentOS Stream 9   | WARN           |
+-------------------+----------------+
| Fedora 40         | WARN           |
+-------------------+----------------+
| Fedora 40 (Clang) | WARN           |
+-------------------+----------------+
| Debian 12         | WARN           |
+-------------------+----------------+
| RHEL8             | WARN           |
+-------------------+----------------+
| Fedora 41         | WARN           |
+-------------------+----------------+
| Fedora 41 (Clang) | WARN           |
+-------------------+----------------+
| RHEL9             | WARN           |
+-------------------+----------------+
| Ubuntu 24.04      | WARN           |
+-------------------+----------------+
| Ubuntu 20.04      | WARN           |
+-------------------+----------------+
| Ubuntu 22.04      | WARN           |
+-------------------+----------------+

==== 20 line log output for Ubuntu 22.04 (dpdk_unit_test): ====
|                                      ^~~~~~~~~~~~~~~~~
../drivers/common/mlx5/mlx5_devx_cmds.c:1352:40: note: in expansion of macro 'MLX5_GET'
1352 |                 attr->fdb_unified_en = MLX5_GET(wqe_based_flow_table_cap,
|                                        ^~~~~~~~
../drivers/common/mlx5/mlx5_prm.h:967:57: error: 'struct mlx5_ifc_wqe_based_flow_table_cap_bits' has no member named 'fdb_unified_en'
967 | #define __mlx5_bit_sz(typ, fld) sizeof(__mlx5_nullp(typ)->fld)
|                                                         ^~
../drivers/common/mlx5/mlx5_prm.h:976:47: note: in expansion of macro '__mlx5_bit_sz'
976 | #define __mlx5_mask(typ, fld) ((u32)((1ull << __mlx5_bit_sz(typ, fld)) - 1))
|                                               ^~~~~~~~~~~~~
../drivers/common/mlx5/mlx5_prm.h:1025:9: note: in expansion of macro '__mlx5_mask'
1025 |         __mlx5_mask(typ, fld))
|         ^~~~~~~~~~~
../drivers/common/mlx5/mlx5_devx_cmds.c:1352:40: note: in expansion of macro 'MLX5_GET'
1352 |                 attr->fdb_unified_en = MLX5_GET(wqe_based_flow_table_cap,
|                                        ^~~~~~~~
[779/3154] Generating rte_common_cnxk.pmd.c with a custom command
[780/3154] Generating rte_bus_fslmc.sym_chk with a custom command (wrapped by meson to capture output)
[781/3154] Compiling C object drivers/libtmp_rte_common_mlx5.a.p/common_mlx5_mlx5_common_mp.c.o
ninja: build stopped: subcommand failed.
==== End log output ====

Debian Bullseye
	Kernel: Depends on container host
	Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110

CentOS Stream 10
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20241104 (Red Hat 14.2.1-6)

CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.8 (Fedora 18.1.8-1.fc40)

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

RHEL8
	Kernel: Depends on container host
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)

Fedora 41
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)

Fedora 41 (Clang)
	Kernel: Depends on container host
	Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

Ubuntu 24.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

Ubuntu 20.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Ubuntu 22.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-02-28 17:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250226083846.4023622-5-ophirmu@nvidia.com>
2025-02-26  8:05 ` |SUCCESS| pw152093-152096 [PATCH V2 4/4] net/mlx5/hws: allow different types in miss validation qemudev
2025-02-26  8:09 ` qemudev
2025-02-26  8:41 ` |SUCCESS| pw152096 " checkpatch
2025-02-26 11:05 ` |FAILURE| " 0-day Robot
2025-02-28 15:34 ` |SUCCESS| pw152093-152096 [PATCH] [V2,4/4] net/mlx5/hws: allow diffe dpdklab
2025-02-28 16:23 ` |WARNING| " dpdklab
2025-02-28 16:23 ` dpdklab
2025-02-28 16:23 ` dpdklab
2025-02-28 16:24 ` dpdklab
2025-02-28 17:18 ` dpdklab
2025-02-28 17:18 ` dpdklab
2025-02-28 17:18 ` dpdklab [this message]
2025-02-28 17:26 ` dpdklab
2025-02-28 17:28 ` dpdklab
2025-02-28 18:05 ` |FAILURE| " dpdklab
2025-02-28 18:09 ` dpdklab
2025-02-28 18:11 ` dpdklab
2025-02-28 18:12 ` dpdklab
2025-02-28 19:07 ` dpdklab
2025-02-28 19:09 ` dpdklab
2025-02-28 19:16 ` 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=67c1efed.170a0220.ec8f6.9741SMTPIN_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).