From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Junlong Wang <wang.junlong1@zte.com.cn>
Subject: |FAILURE| pw155740-155741 [PATCH] [v4,2/2] net/zxdh: add support flo
Date: Fri, 08 Aug 2025 05:37:23 -0700 (PDT) [thread overview]
Message-ID: <6895ef83.050a0220.7b6f0.7c84SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250808071048.1906724-3-wang.junlong1@zte.com.cn>
Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/155741
_Testing issues_
Submitter: Junlong Wang <wang.junlong1@zte.com.cn>
Date: Friday, August 08 2025 07:10:37
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:80e868e475c070ddc6928d33acfd68f6a51ae4fe
155740-155741 --> testing issues
Upstream job id: Generic-DPDK-Compile-Meson#416087
Test environment and result as below:
+------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+==============================+====================+
| Red Hat Enterprise Linux 9.5 | FAIL |
+------------------------------+--------------------+
| Ubuntu 20.04 | FAIL |
+------------------------------+--------------------+
| Debian GNU/Linux 12 | FAIL |
+------------------------------+--------------------+
| Fedora Linux 40 | FAIL |
+------------------------------+--------------------+
| Fedora Linux 41 | FAIL |
+------------------------------+--------------------+
| Ubuntu 22.04 | FAIL |
+------------------------------+--------------------+
| Ubuntu 24.04 | FAIL |
+------------------------------+--------------------+
| CentOS Stream 9 | FAIL |
+------------------------------+--------------------+
| CentOS Stream 10 | FAIL |
+------------------------------+--------------------+
==== 20 line log output for CentOS Stream 10 (dpdk_meson_compile): ====
../drivers/net/zxdh/zxdh_flow.c:664:25: error: implicit declaration of function 'free' [-Wimplicit-function-declaration]
664 | free(result);
| ^~~~
../drivers/net/zxdh/zxdh_flow.c:664:25: note: include '<stdlib.h>' or provide a declaration of 'free'
../drivers/net/zxdh/zxdh_flow.c:664:25: error: incompatible implicit declaration of built-in function 'free' [-Werror=builtin-declaration-mismatch]
../drivers/net/zxdh/zxdh_flow.c:664:25: note: include '<stdlib.h>' or provide a declaration of 'free'
../drivers/net/zxdh/zxdh_flow.c:669:33: error: incompatible implicit declaration of built-in function 'calloc' [-Werror=builtin-declaration-mismatch]
669 | entry = calloc(1, sizeof(struct rte_flow));
| ^~~~~~
../drivers/net/zxdh/zxdh_flow.c:669:33: note: include '<stdlib.h>' or provide a declaration of 'calloc'
../drivers/net/zxdh/zxdh_flow.c:677:25: error: incompatible implicit declaration of built-in function 'free' [-Werror=builtin-declaration-mismatch]
677 | free(entry_flow);
| ^~~~
../drivers/net/zxdh/zxdh_flow.c:677:25: note: include '<stdlib.h>' or provide a declaration of 'free'
../drivers/net/zxdh/zxdh_flow.c:685:9: error: incompatible implicit declaration of built-in function 'free' [-Werror=builtin-declaration-mismatch]
685 | free(result);
| ^~~~
../drivers/net/zxdh/zxdh_flow.c:685:9: note: include '<stdlib.h>' or provide a declaration of 'free'
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 40
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora Linux 41
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.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-7)
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/33842/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2025-08-08 12:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250808071048.1906724-3-wang.junlong1@zte.com.cn>
2025-08-08 6:51 ` |SUCCESS| pw155740-155741 [PATCH v4 2/2] net/zxdh: add support flow director ops qemudev
2025-08-08 6:56 ` qemudev
2025-08-08 7:21 ` |WARNING| pw155741 " checkpatch
2025-08-08 8:01 ` |SUCCESS| pw155740-155741 [PATCH] [v4,2/2] net/zxdh: add support flo dpdklab
2025-08-08 8:05 ` |PENDING| " dpdklab
2025-08-08 8:07 ` |SUCCESS| " dpdklab
2025-08-08 8:08 ` |PENDING| " dpdklab
2025-08-08 8:09 ` dpdklab
2025-08-08 8:22 ` |SUCCESS| " dpdklab
2025-08-08 8:24 ` dpdklab
2025-08-08 8:24 ` dpdklab
2025-08-08 8:32 ` dpdklab
2025-08-08 8:33 ` dpdklab
2025-08-08 8:34 ` |FAILURE| " dpdklab
2025-08-08 8:47 ` dpdklab
2025-08-08 8:47 ` dpdklab
2025-08-08 8:53 ` |SUCCESS| " dpdklab
2025-08-08 8:59 ` dpdklab
2025-08-08 9:04 ` dpdklab
2025-08-08 9:50 ` |FAILURE| " dpdklab
2025-08-08 10:56 ` |WARNING| " dpdklab
2025-08-08 12:13 ` |SUCCESS| " dpdklab
2025-08-08 12:37 ` dpdklab [this message]
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=6895ef83.050a0220.7b6f0.7c84SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=wang.junlong1@zte.com.cn \
/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).