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| pw154831-154835 [PATCH] [v5,5/5] net/mlx5: use consecutive
Date: Sun, 29 Jun 2025 13:43:19 -0700 (PDT) [thread overview]
Message-ID: <6861a567.050a0220.11fb4.6bf3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250629172303.72049-6-bingz@nvidia.com>
Test-Label: iol-abi-testing
Test-Status: FAILURE
http://dpdk.org/patch/154835
_Testing issues_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Sunday, June 29 2025 17:23:03
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5c0c1a13c34aa57c6e18f9ba852a9b5807c58b72
154831-154835 --> testing issues
Upstream job id: Generic-DPDK-Compile-ABI#132288
Test environment and result as below:
+-------------------------------+----------+
| Environment | abi_test |
+===============================+==========+
| CentOS Stream 9 | FAIL |
+-------------------------------+----------+
| CentOS Stream 10 | FAIL |
+-------------------------------+----------+
| Debian GNU/Linux 12 | FAIL |
+-------------------------------+----------+
| Fedora Linux 40 | FAIL |
+-------------------------------+----------+
| openSUSE Leap 15.6 | FAIL |
+-------------------------------+----------+
| Fedora Linux 41 | FAIL |
+-------------------------------+----------+
| Red Hat Enterprise Linux 9.5 | FAIL |
+-------------------------------+----------+
| Red Hat Enterprise Linux 8.10 | FAIL |
+-------------------------------+----------+
| Ubuntu 24.04 | FAIL |
+-------------------------------+----------+
| Ubuntu 22.04 | FAIL |
+-------------------------------+----------+
==== 20 line log output for Ubuntu 22.04 (abi_test): ====
[1975/3705] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_meter.c.o
[1976/3705] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_mac.c.o
[1977/3705] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_nta_rss.c.o
[1978/3705] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rss.c.o
[1979/3705] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rx.c.o
[1980/3705] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rxmode.c.o
[1981/3705] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rxq.c.o
[1982/3705] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rxtx.c.o
[1983/3705] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_stats.c.o
[1984/3705] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_trace.c.o
[1985/3705] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_trigger.c.o
FAILED: drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_trigger.c.o
ccache cc -Idrivers/libtmp_rte_net_mlx5.a.p -Idrivers -I../drivers -Idrivers/net/mlx5 -I../drivers/net/mlx5 -Idrivers/net/mlx5/linux -I../drivers/net/mlx5/linux -Idrivers/net/mlx5/hws -I../drivers/net/mlx5/hws -Ilib/ethdev -I../lib/ethdev -Ilib/eal/common -I../lib/eal/common -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include -I../kernel/linux -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/meter -I../lib/meter -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/pci -I../lib/pci -Idrivers/bus/vdev -I../drivers/bus/vdev -Ilib/hash -I../lib/hash -Ilib/rcu -I../lib/rcu -Idrivers/common/mlx5 -I../drivers/common/mlx5 -Idrivers/common/mlx5/linux -I../drivers
/common/mlx5/linux -Idrivers/bus/auxiliary -I../drivers/bus/auxiliary -I/usr/include/libnl3 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c11 -O2 -g -include rte_config.h -Wvla -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=native -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -Wno-address-of-packed-member -std=c11 -Wno-strict-prototypes -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -pedantic -DPEDANTIC -Wno-vla -DRTE_LOG_DEFAULT_LOGTYPE=pmd.net.mlx5 -MD -MQ drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_trigger.c.o -MF drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_trigger.c.o.d -o drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_trigger.c.o -c ../d
rivers/net/mlx5/mlx5_trigger.c
../drivers/net/mlx5/mlx5_trigger.c: In function 'mlx5_dev_allocate_consec_tx_mem':
../drivers/net/mlx5/mlx5_trigger.c:1162:63: error: expected ';' before ')' token
1162 | alignment = (size_t)1 << priv->sh->config.txq_mem_algn);
| ^
| ;
../drivers/net/mlx5/mlx5_trigger.c:1162:63: error: expected statement before ')' token
ninja: build stopped: subcommand failed.
==== End log output ====
CentOS Stream 9
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-7)
CentOS Stream 10
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-8)
Debian GNU/Linux 12
Kernel: 5.15
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
Fedora Linux 40
Kernel: 5.15
Compiler: clang gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
openSUSE Leap 15.6
Kernel: 5.15
Compiler: gcc gcc (SUSE Linux) 7.5.0
Fedora Linux 41
Kernel: 5.15
Compiler: clang gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
Red Hat Enterprise Linux 9.5
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)
Red Hat Enterprise Linux 8.10
Kernel: 5.15
Compiler: gcc gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-22)
Ubuntu 24.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33535/
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-06-29 20:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250629172303.72049-6-bingz@nvidia.com>
2025-06-29 16:49 ` |SUCCESS| pw154831-154835 [PATCH v5 5/5] net/mlx5: use consecutive memory for Tx queue creation qemudev
2025-06-29 16:54 ` qemudev
2025-06-29 17:23 ` |SUCCESS| pw154835 " checkpatch
2025-06-29 18:02 ` |FAILURE| " 0-day Robot
2025-06-29 19:41 ` |FAILURE| pw154831-154835 [PATCH] [v5,5/5] net/mlx5: use consecutive dpdklab
2025-06-29 19:57 ` dpdklab
2025-06-29 20:07 ` dpdklab
2025-06-29 20:15 ` |PENDING| " dpdklab
2025-06-29 20:24 ` |FAILURE| " dpdklab
2025-06-29 20:24 ` dpdklab
2025-06-29 20:27 ` dpdklab
2025-06-29 20:31 ` dpdklab
2025-06-29 20:33 ` dpdklab
2025-06-29 20:42 ` dpdklab
2025-06-29 20:42 ` dpdklab
2025-06-29 20:43 ` dpdklab [this message]
2025-06-29 20:45 ` |PENDING| " dpdklab
2025-06-29 21:01 ` |FAILURE| " dpdklab
2025-06-29 21:20 ` |WARNING| " dpdklab
2025-06-29 22:25 ` |FAILURE| " dpdklab
2025-06-29 22:54 ` |WARNING| " dpdklab
2025-06-29 22:54 ` dpdklab
2025-06-29 23:19 ` |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=6861a567.050a0220.11fb4.6bf3SMTPIN_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).