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,
	Anatoly Burakov <anatoly.burakov@intel.com>
Subject: |FAILURE| pw158794-158812 [PATCH] [v2,19/19] vfio: introduce cdev mo
Date: Sat, 15 Nov 2025 06:39:25 -0800 (PST)	[thread overview]
Message-ID: <6918909d.170a0220.3a97bd.bb65SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <45db9c5e1589c56ed0e31a0e15390da5366ca5c2.1763142008.git.anatoly.burakov@intel.com>

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

_Testing issues_

Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Friday, November 14 2025 17:40:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:be0112878b4fc3a1b918370ed2fe615c52039d77

158794-158812 --> testing issues

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

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 42              | 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): ====
131 |                         free(mp_reply.msgs);
|                         ^~~~
../lib/eal/linux/eal_vfio_cdev.c:131:25: note: include '<stdlib.h>' or provide a declaration of 'free'
../lib/eal/linux/eal_vfio_cdev.c:136:9: error: incompatible implicit declaration of built-in function 'free' [-Werror=builtin-declaration-mismatch]
136 |         free(mp_reply.msgs);
|         ^~~~
../lib/eal/linux/eal_vfio_cdev.c:136:9: note: include '<stdlib.h>' or provide a declaration of 'free'
../lib/eal/linux/eal_vfio_cdev.c: In function 'vfio_cdev_get_device_num':
../lib/eal/linux/eal_vfio_cdev.c:234:35: error: implicit declaration of function 'strtol'; did you mean 'strtok'? [-Wimplicit-function-declaration]
234 |                         dev_num = strtol(dev_tok, &end, 10);
|                                   ^~~~~~
|                                   strtok
../lib/eal/linux/eal_vfio_cdev.c:234:35: error: nested extern declaration of 'strtol' [-Werror=nested-externs]
../lib/eal/linux/eal_vfio_cdev.c: In function 'vfio_cdev_request_dev_fd':
../lib/eal/linux/eal_vfio_cdev.c:359:9: error: incompatible implicit declaration of built-in function 'free' [-Werror=builtin-declaration-mismatch]
359 |         free(mp_reply.msgs);
|         ^~~~
../lib/eal/linux/eal_vfio_cdev.c:359: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 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/34593/

UNH-IOL DPDK Community Lab

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

      parent reply	other threads:[~2025-11-15 14:39 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <45db9c5e1589c56ed0e31a0e15390da5366ca5c2.1763142008.git.anatoly.burakov@intel.com>
2025-11-14 17:10 ` |SUCCESS| pw158794-158812 [PATCH v2 19/19] vfio: introduce cdev mode qemudev
2025-11-14 17:15 ` qemudev
2025-11-14 17:44 ` |SUCCESS| pw158812 " checkpatch
2025-11-14 18:12 ` |FAILURE| pw158794-158812 [PATCH] [v2,19/19] vfio: introduce cdev mo dpdklab
2025-11-14 18:15 ` dpdklab
2025-11-14 18:16 ` |SUCCESS| " dpdklab
2025-11-14 18:22 ` |FAILURE| " dpdklab
2025-11-14 18:24 ` |PENDING| " dpdklab
2025-11-14 18:27 ` |SUCCESS| " dpdklab
2025-11-14 18:36 ` dpdklab
2025-11-14 18:40 ` |PENDING| " dpdklab
2025-11-14 18:48 ` |FAILURE| pw158812 [PATCH v2 19/19] vfio: introduce cdev mode 0-day Robot
2025-11-14 18:52 ` |SUCCESS| pw158794-158812 [PATCH] [v2,19/19] vfio: introduce cdev mo dpdklab
2025-11-14 19:04 ` dpdklab
2025-11-14 19:11 ` |FAILURE| " dpdklab
2025-11-14 19:14 ` dpdklab
2025-11-14 19:46 ` |SUCCESS| " dpdklab
2025-11-14 21:33 ` dpdklab
2025-11-15  0:58 ` |FAILURE| " dpdklab
2025-11-15  4:26 ` dpdklab
2025-11-15  5:00 ` dpdklab
2025-11-15  8:09 ` |SUCCESS| " dpdklab
2025-11-15  8:21 ` dpdklab
2025-11-15 10:48 ` |FAILURE| " dpdklab
2025-11-15 11:05 ` dpdklab
2025-11-15 13:18 ` dpdklab
2025-11-15 13:24 ` dpdklab
2025-11-15 14:39 ` dpdklab
2025-11-15 14:39 ` dpdklab
2025-11-15 14:39 ` 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=6918909d.170a0220.3a97bd.bb65SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=anatoly.burakov@intel.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).