From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Miao Li <miao.li@intel.com>
Subject: |FAILURE| pw126851-126854 [PATCH] [v2, 4/4] bus/pci: add VFIO sparse mmap support
Date: Mon, 15 May 2023 03:53:01 -0700 (PDT) [thread overview]
Message-ID: <64620f0d.020a0220.49c0.4ce8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-x86_64-compile-testing
Test-Status: FAILURE
http://dpdk.org/patch/126854
_Testing issues_
Submitter: Miao Li <miao.li@intel.com>
Date: Monday, May 15 2023 09:41:24
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:dbff181d62c997f128b75db2bbac9f42e8dd0f8f
126851-126854 --> testing fail
Test environment and result as below:
+------------------+--------------------+
| Environment | dpdk_meson_compile |
+==================+====================+
| FreeBSD 13 | PASS |
+------------------+--------------------+
| Debian Bullseye | PASS |
+------------------+--------------------+
| CentOS Stream 8 | PASS |
+------------------+--------------------+
| Ubuntu 22.04 | PASS |
+------------------+--------------------+
| CentOS Stream 9 | PASS |
+------------------+--------------------+
| openSUSE Leap 15 | PASS |
+------------------+--------------------+
| Alpine | PASS |
+------------------+--------------------+
| Debian Buster | PASS |
+------------------+--------------------+
| RHEL 7 | FAIL |
+------------------+--------------------+
| RHEL8 | PASS |
+------------------+--------------------+
| Ubuntu 20.04 | PASS |
+------------------+--------------------+
==== 20 line log output for RHEL 7 (dpdk_meson_compile): ====
[625/3218] Linking target drivers/librte_bus_fslmc.so.23.2.
[626/3218] Generating symbol file 'drivers/a715181@@rte_bus_fslmc@sha/librte_bus_fslmc.so.23.2.symbols'.
[627/3218] Compiling C object 'drivers/a715181@@rte_bus_ifpga@sha/meson-generated_.._rte_bus_ifpga.pmd.c.o'.
[628/3218] Linking target drivers/librte_bus_ifpga.so.23.2.
[629/3218] Compiling C object 'drivers/a715181@@tmp_rte_bus_pci@sta/bus_pci_pci_params.c.o'.
[630/3218] Compiling C object 'drivers/a715181@@tmp_rte_bus_pci@sta/bus_pci_pci_common_uio.c.o'.
[631/3218] Compiling C object 'drivers/a715181@@tmp_rte_bus_pci@sta/bus_pci_linux_pci.c.o'.
[632/3218] Compiling C object 'drivers/a715181@@tmp_rte_bus_pci@sta/bus_pci_linux_pci_uio.c.o'.
[633/3218] Compiling C object 'drivers/a715181@@tmp_rte_bus_pci@sta/bus_pci_linux_pci_vfio.c.o'.
FAILED: drivers/a715181@@tmp_rte_bus_pci@sta/bus_pci_linux_pci_vfio.c.o
ccache cc -Idrivers/a715181@@tmp_rte_bus_pci@sta -Idrivers -I../drivers -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -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 -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/telemetry/../metrics -I../lib/telemetry/../metrics -Ilib/telemetry -I../lib/telemetry -Ilib/pci -I../lib/pci -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -O3 -include rte_config.h -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-missing-field-initializers -D_GNU_SOURCE -fPIC -march=native -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -DRTE_LOG_DEFAULT_LOGTYPE=bus.pci -MD -MQ 'drivers/a71
5181@@tmp_rte_bus_pci@sta/bus_pci_linux_pci_vfio.c.o' -MF 'drivers/a715181@@tmp_rte_bus_pci@sta/bus_pci_linux_pci_vfio.c.o.d' -o 'drivers/a715181@@tmp_rte_bus_pci@sta/bus_pci_linux_pci_vfio.c.o' -c ../drivers/bus/pci/linux/pci_vfio.c
../drivers/bus/pci/linux/pci_vfio.c: In function 'pci_vfio_map_resource_primary':
../drivers/bus/pci/linux/pci_vfio.c:779:11: error: 'info' may be used uninitialized in this function [-Werror=maybe-uninitialized]
if ((info->flags & RTE_VFIO_INFO_FLAG_CAPS) == 0) {
^
../drivers/bus/pci/linux/pci_vfio.c:797:27: note: 'info' was declared here
struct vfio_region_info *info;
^
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 12.2.1-2
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26225/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-05-15 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 10:53 dpdklab [this message]
2023-05-15 11:28 dpdklab
2023-05-15 17:56 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=64620f0d.020a0220.49c0.4ce8SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=miao.li@intel.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).