From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw149589-149603 [PATCH] [v4,15/15] net/xsc: add ethdev lin
Date: Fri, 03 Jan 2025 15:47:23 -0800 (PST) [thread overview]
Message-ID: <6778770b.050a0220.d4d5.3ab9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250103150436.1529663-16-wanry@yunsilicon.com>
Test-Label: iol-unit-amd64-testing
Test-Status: WARNING
http://dpdk.org/patch/149603
_Testing issues_
Submitter: WanRenyong <wanry@yunsilicon.com>
Date: Friday, January 03 2025 15:04:37
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:94ad302b4ebba4a5b6706a1c43ea0505e5098169
149589-149603 --> testing issues
Upstream job id: Generic-Unit-Test-DPDK#303500
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Fedora 40 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Fedora 41 (Clang) | WARN |
+---------------------+----------------+
| Fedora 40 (Clang) | WARN |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| RHEL9 | PASS |
+---------------------+----------------+
| Fedora 41 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| Debian 12 | PASS |
+---------------------+----------------+
| Ubuntu 24.04 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
==== 20 line log output for Fedora 40 (Clang) (dpdk_unit_test): ====
[2274/3153] Linking static target drivers/librte_net_vmxnet3.a
[2275/3153] Compiling C object drivers/librte_net_vmxnet3.so.25.1.p/meson-generated_.._rte_net_vmxnet3.pmd.c.o
[2276/3153] Linking target drivers/librte_net_vmxnet3.so.25.1
[2277/3153] Generating rte_net_virtio.pmd.c with a custom command
[2278/3153] Compiling C object drivers/librte_net_virtio.a.p/meson-generated_.._rte_net_virtio.pmd.c.o
[2279/3153] Compiling C object drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_vfio_mbox.c.o
[2280/3153] Linking static target drivers/librte_net_virtio.a
[2281/3153] Compiling C object drivers/librte_net_virtio.so.25.1.p/meson-generated_.._rte_net_virtio.pmd.c.o
[2282/3153] Linking target drivers/librte_net_virtio.so.25.1
[2283/3153] Compiling C object drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_vfio.c.o
FAILED: drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_vfio.c.o
clang -Idrivers/libtmp_rte_net_xsc.a.p -Idrivers -I../drivers -Idrivers/net/xsc -I../drivers/net/xsc -Ilib/ethdev -I../lib/ethdev -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/common -I../lib/eal/common -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 -Xclang -fcolor-diagnostics -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -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 -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -Wno-address-of-packed-member -DRTE_LOG_DEFAULT_LOGTYPE=pmd.net.xsc -DRTE_ANNOTATE_LOCKS -Wthread-safety -MD -MQ drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_vfio.c.o -MF drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_vfio.c.o.d -o drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_vfio.c.o -c ../drivers/net/xsc/xsc_vfio.c
../drivers/net/xsc/xsc_vfio.c:482:26: error: cast from 'volatile struct xsc_cqe (*)[]' to 'void *' drops volatile qualifier [-Werror,-Wcast-qual]
482 | cq_info->cqes = (void *)cqes;
| ^
1 error generated.
[2284/3153] Compiling C object drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_np.c.o
[2285/3153] Compiling C object drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_rx.c.o
[2286/3153] Compiling C object drivers/libtmp_rte_net_xsc.a.p/net_xsc_xsc_tx.c.o
ninja: build stopped: subcommand failed.
==== End log output ====
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
Debian Bullseye
Kernel: Depends on container host
Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
Fedora 41 (Clang)
Kernel: Depends on container host
Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.8 (Fedora 18.1.8-1.fc40)
RHEL8
Kernel: Depends on container host
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
Fedora 41
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
Ubuntu 22.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Ubuntu 24.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32248/
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-01-03 23:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250103150436.1529663-16-wanry@yunsilicon.com>
2025-01-03 14:35 ` |SUCCESS| pw149589-149603 [PATCH v4 15/15] net/xsc: add ethdev link and MTU ops qemudev
2025-01-03 14:40 ` qemudev
2025-01-03 15:07 ` |SUCCESS| pw149603 " checkpatch
2025-01-03 16:04 ` |FAILURE| " 0-day Robot
2025-01-03 22:23 ` |SUCCESS| pw149589-149603 [PATCH] [v4,15/15] net/xsc: add ethdev lin dpdklab
2025-01-03 22:36 ` dpdklab
2025-01-03 22:38 ` dpdklab
2025-01-03 22:40 ` |PENDING| " dpdklab
2025-01-03 22:45 ` |SUCCESS| " dpdklab
2025-01-03 22:48 ` dpdklab
2025-01-03 22:53 ` dpdklab
2025-01-03 22:58 ` |PENDING| " dpdklab
2025-01-03 23:09 ` |SUCCESS| " dpdklab
2025-01-03 23:16 ` dpdklab
2025-01-03 23:23 ` |PENDING| " dpdklab
2025-01-03 23:28 ` |SUCCESS| " dpdklab
2025-01-03 23:31 ` |PENDING| " dpdklab
2025-01-03 23:33 ` |SUCCESS| " dpdklab
2025-01-03 23:38 ` |PENDING| " dpdklab
2025-01-03 23:47 ` dpdklab [this message]
2025-01-03 23:56 ` |FAILURE| " dpdklab
2025-01-04 0:00 ` |SUCCESS| " dpdklab
2025-01-04 0:19 ` dpdklab
2025-01-04 0:33 ` |WARNING| " dpdklab
2025-01-04 0:35 ` |FAILURE| " dpdklab
2025-01-04 1:05 ` 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=6778770b.050a0220.d4d5.3ab9SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--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).