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, Maayan Kashani <mkashani@nvidia.com>
Subject: |FAILURE| pw156507-156509 [PATCH] [v2,3/3] net/mlx5: fix ESP header
Date: Tue, 09 Sep 2025 05:07:03 -0700 (PDT)	[thread overview]
Message-ID: <68c01867.810a0220.16ddab.a86eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250909062853.60592-3-mkashani@nvidia.com>

Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/156509

_Testing issues_

Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Tuesday, September 09 2025 06:28:53 
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: master
  CommitID:14681e14e4b3d52bf696e684fc673a522e959677

156507-156509 --> testing issues

Upstream job id: Generic-DPDK-Compile-Meson#423522

Test environment and result as below:

+------------------------------+--------------------+
|         Environment          | dpdk_meson_compile |
+==============================+====================+
| Red Hat Enterprise Linux 9.5 | PASS               |
+------------------------------+--------------------+
| Ubuntu 20.04                 | PASS               |
+------------------------------+--------------------+
| Debian GNU/Linux 12          | FAIL               |
+------------------------------+--------------------+
| Fedora Linux 42              | PASS               |
+------------------------------+--------------------+
| Ubuntu 22.04                 | PASS               |
+------------------------------+--------------------+
| Ubuntu 24.04                 | PASS               |
+------------------------------+--------------------+
| CentOS Stream 9              | PASS               |
+------------------------------+--------------------+
| CentOS Stream 10             | PASS               |
+------------------------------+--------------------+

==== 20 line log output for Debian GNU/Linux 12 (dpdk_meson_compile): ====
[2596/3783] Generating rte_net_vmxnet3_map with a custom command
[2597/3783] Generating rte_net_vmxnet3.sym_chk with a custom command (wrapped by meson to capture output)
[2598/3783] Compiling C object drivers/librte_net_vmxnet3.so.26.0.p/meson-generated_.._rte_net_vmxnet3.pmd.c.o
[2599/3783] Linking target drivers/librte_net_vmxnet3.so.26.0
[2600/3783] Compiling C object drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_ethdev.c.o
[2601/3783] Compiling C object drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_dev.c.o
[2602/3783] Compiling C object drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_vfio_mbox.c.o
[2603/3783] Compiling C object drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_vfio.c.o
[2604/3783] Compiling C object drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_np.c.o
[2605/3783] Compiling C object drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_rx.c.o
FAILED: drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_rx.c.o
ccache cc -Idrivers/libtmp_rte_net_xsc.a.p -Idrivers -I../drivers -Idrivers/net/xsc -I../drivers/net/xsc -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/arm/include -I../lib/eal/arm/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 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O3 -include rte_config.h -Wvla -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-pr
 ototypes -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=armv8.1-a+crc+crypto -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -Wno-address-of-packed-member -Wno-vla -DRTE_LOG_DEFAULT_LOGTYPE=pmd.net.xsc -MD -MQ drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_rx.c.o -MF drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_rx.c.o.d -o drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_rx.c.o -c ../drivers/net/xsc/xsc_rx.c
In function 'xsc_rss_qp_create',
inlined from 'xsc_rxq_rss_obj_new' at ../drivers/net/xsc/xsc_rx.c:565:8:
../drivers/net/xsc/xsc_rx.c:501:9: error: pointer 'req' may be used after 'free' [-Werror=use-after-free]
501 |         free(req);
|         ^~~~~~~~~
../drivers/net/xsc/xsc_rx.c:501:9: note: call to 'free' here
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====

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

Ubuntu 20.04
	Kernel: 5.15
	Compiler: aarch64-linux-gnu-gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

Fedora Linux 42
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 15.2.1 20250808 (Red Hat 15.2.1-1)

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-09-09 12:07 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250909062853.60592-3-mkashani@nvidia.com>
2025-09-09  5:55 ` |SUCCESS| pw156507-156509 [PATCH v2 3/3] net/mlx5: fix ESP header match after UDP for group 0 qemudev
2025-09-09  6:00 ` qemudev
2025-09-09  6:27 ` |SUCCESS| pw156509 " checkpatch
2025-09-09  6:59 ` |SUCCESS| pw156507-156509 [PATCH] [v2,3/3] net/mlx5: fix ESP header dpdklab
2025-09-09  7:01 ` dpdklab
2025-09-09  7:03 ` |PENDING| " dpdklab
2025-09-09  7:06 ` |SUCCESS| " dpdklab
2025-09-09  7:06 ` dpdklab
2025-09-09  7:27 ` dpdklab
2025-09-09  7:33 ` dpdklab
2025-09-09  7:34 ` |PENDING| " dpdklab
2025-09-09  7:36 ` dpdklab
2025-09-09  7:36 ` |FAILURE| " dpdklab
2025-09-09  7:56 ` |SUCCESS| " dpdklab
2025-09-09  7:59 ` |SUCCESS| pw156509 [PATCH v2 3/3] net/mlx5: fix ESP header match after UDP for group 0 0-day Robot
2025-09-09  7:59 ` 0-day Robot
2025-09-09  8:01 ` |SUCCESS| pw156507-156509 [PATCH] [v2,3/3] net/mlx5: fix ESP header dpdklab
2025-09-09  8:11 ` |FAILURE| " dpdklab
2025-09-09  8:19 ` |WARNING| " dpdklab
2025-09-09  8:21 ` |SUCCESS| " dpdklab
2025-09-09  8:40 ` dpdklab
2025-09-09  8:42 ` |FAILURE| " dpdklab
2025-09-09  8:50 ` dpdklab
2025-09-09  8:56 ` |SUCCESS| " dpdklab
2025-09-09 10:55 ` |FAILURE| " dpdklab
2025-09-09 12:07 ` dpdklab [this message]
2025-09-09 12:42 ` |WARNING| " 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=68c01867.810a0220.16ddab.a86eSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=mkashani@nvidia.com \
    --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).