From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: longli@linuxonhyperv.com, robot@bytheb.org
Subject: |FAILURE| pw152845 [patch v5 6/6] bus/vmbus: set event for channel without monitoring support
Date: Tue, 8 Apr 2025 18:43:39 -0400 [thread overview]
Message-ID: <20250408224339.1407908-1-robot@bytheb.org> (raw)
In-Reply-To: <1744149236-30264-7-git-send-email-longli@linuxonhyperv.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/152845/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/14344471458
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-abi+debug+doc+examples+tests" failed at step Build and test
"ubuntu-22.04-gcc-stdatomic" failed at step Build and test
"ubuntu-22.04-clang-stdatomic" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
parameter 5 of type 'typedef uint32_t' changed:
entity changed from 'typedef uint32_t' to 'void*'
type size changed from 32 to 0 (in bits)
parameter 6 of type 'typedef uint64_t' changed:
typedef name changed from uint64_t to uint32_t at stdint-uintn.h:26:1
underlying type 'typedef __uint64_t' changed at types.h:45:1, as reported earlier
parameter 7 of type 'bool*' changed:
entity changed from 'bool*' to 'typedef uint64_t' at stdint-uintn.h:27:1
type size hasn't changed
parameter 8 of type 'bool*' was added
[C] 'function void rte_vmbus_chan_signal_read(vmbus_channel*, uint32_t)' at vmbus_channel.c:191:1 has some indirect sub-type changes:
parameter 2 of type 'typedef uint32_t' changed:
entity changed from 'typedef uint32_t' to 'vmbus_channel*'
type size changed from 32 to 64 (in bits)
parameter 3 of type 'typedef uint32_t' was added
[C] 'function void rte_vmbus_chan_signal_tx(const vmbus_channel*)' at vmbus_channel.c:80:1 has some indirect sub-type changes:
parameter 1 of type 'const vmbus_channel*' changed:
in pointed to type 'const vmbus_channel' at bus_vmbus_driver.h:33:1:
entity changed from 'const vmbus_channel' to 'struct rte_vmbus_device' at bus_vmbus_driver.h:33:1
type size changed from 640 to 2304 (in bits)
parameter 2 of type 'const vmbus_channel*' was added
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-stdatomic" at step Build and test
####################################################################################
[449/3553] Compiling C object lib/librte_port.a.p/port_rte_swx_port_ring.c.o
[450/3553] Generating rte_bus_ifpga.pmd.c with a custom command
[451/3553] Generating rte_bus_vdev.pmd.c with a custom command
[452/3553] Compiling C object drivers/libtmp_rte_common_ionic.a.p/common_ionic_ionic_common_uio.c.o
[453/3553] Compiling C object lib/librte_port.a.p/port_rte_swx_port_source_sink.c.o
[454/3553] Linking static target lib/librte_port.a
[455/3553] Compiling C object drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_vmbus_bufring.c.o
[456/3553] Linking static target drivers/librte_common_cnxk.a
[457/3553] Compiling C object drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_linux_vmbus_bus.c.o
[458/3553] Compiling C object drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_vmbus_common.c.o
[459/3553] Compiling C object drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_vmbus_channel.c.o
FAILED: drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_vmbus_channel.c.o
ccache gcc -Idrivers/libtmp_rte_bus_vmbus.a.p -Idrivers -I../drivers -Idrivers/bus/vmbus -I../drivers/bus/vmbus -I../drivers/bus/vmbus/linux -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/x86/include -I../lib/eal/x86/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 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O2 -g -include rte_config.h -Wvla -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-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=corei7 -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -Wno-address-of-packed-member -DRTE_LOG_DEFAULT_LOGTYPE=bus.vmbus -MD -MQ drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_vmbus_channel.c.o -MF drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_vmbus_channel.c.o.d -o drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_vmbus_channel.c.o -c ../drivers/bus/vmbus/vmbus_channel.c
../drivers/bus/vmbus/vmbus_channel.c: In function ‘vmbus_set_monitor’:
../drivers/bus/vmbus/vmbus_channel.c:51:22: error: assignment to ‘uint32_t *’ {aka ‘unsigned int *’} from incompatible pointer type ‘_Atomic uint32_t *’ {aka ‘_Atomic unsigned int *’} [-Werror=incompatible-pointer-types]
51 | monitor_addr = &channel->monitor_page->trigs[trigger_index].pending;
| ^
cc1: all warnings being treated as errors
[460/3553] Generating rte_common_cnxk_map with a custom command
[461/3553] Compiling C object drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_vmbus_common_uio.c.o
[462/3553] Compiling C object drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_linux_vmbus_uio.c.o
[463/3553] Compiling C object drivers/libtmp_rte_common_mlx5.a.p/common_mlx5_mlx5_common.c.o
[464/3553] Compiling C object drivers/libtmp_rte_common_mlx5.a.p/common_mlx5_mlx5_devx_cmds.c.o
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-stdatomic" at step Build and test
####################################################################################
####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-stdatomic" at step Build and test
####################################################################################
[454/3553] Linking static target lib/librte_port.a
[455/3553] Compiling C object drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_vmbus_common.c.o
[456/3553] Compiling C object drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_vmbus_channel.c.o
FAILED: drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_vmbus_channel.c.o
ccache clang -Idrivers/libtmp_rte_bus_vmbus.a.p -Idrivers -I../drivers -Idrivers/bus/vmbus -I../drivers/bus/vmbus -I../drivers/bus/vmbus/linux -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/x86/include -I../lib/eal/x86/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 -Xclang -fcolor-diagnostics -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O2 -g -include rte_config.h -Wvla -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=corei7 -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-address-of-packed-member -DRTE_LOG_DEFAULT_LOGTYPE=bus.vmbus -DRTE_ANNOTATE_LOCKS -Wthread-safety -MD -MQ drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_vmbus_channel.c.o -MF drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_vmbus_channel.c.o.d -o drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_vmbus_channel.c.o -c ../drivers/bus/vmbus/vmbus_channel.c
../drivers/bus/vmbus/vmbus_channel.c:25:2: error: address argument to atomic operation must be a pointer to _Atomic type ('uint32_t *' (aka 'unsigned int *') invalid)
rte_atomic_fetch_or_explicit(addr, mask, rte_memory_order_seq_cst);
^ ~~~~
../lib/eal/include/rte_stdatomic.h:100:2: note: expanded from macro 'rte_atomic_fetch_or_explicit'
atomic_fetch_or_explicit(ptr, val, memorder)
^ ~~~
/usr/lib/llvm-14/lib/clang/14.0.0/include/stdatomic.h:148:34: note: expanded from macro 'atomic_fetch_or_explicit'
#define atomic_fetch_or_explicit __c11_atomic_fetch_or
^
../drivers/bus/vmbus/vmbus_channel.c:51:15: error: incompatible pointer types assigning to '_Atomic(uint32_t *)' from '_Atomic(uint32_t) *' [-Werror,-Wincompatible-pointer-types]
monitor_addr = &channel->monitor_page->trigs[trigger_index].pending;
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2 errors generated.
[457/3553] Compiling C object drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_vmbus_bufring.c.o
[458/3553] Linking static target drivers/librte_common_cnxk.a
[459/3553] Compiling C object drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_vmbus_common_uio.c.o
[460/3553] Compiling C object drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_linux_vmbus_bus.c.o
[461/3553] Compiling C object drivers/libtmp_rte_bus_vmbus.a.p/bus_vmbus_linux_vmbus_uio.c.o
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-clang-stdatomic" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2025-04-08 22:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1744149236-30264-7-git-send-email-longli@linuxonhyperv.com>
2025-04-08 21:26 ` |SUCCESS| pw152840-152845 " qemudev
2025-04-08 21:31 ` qemudev
2025-04-08 21:56 ` |SUCCESS| pw152845 " checkpatch
2025-04-08 22:43 ` 0-day Robot [this message]
2025-04-09 2:35 ` |SUCCESS| pw152840-152845 [PATCH] [v5,6/6] bus/vmbus: set event for dpdklab
2025-04-09 2:44 ` dpdklab
2025-04-09 2:48 ` dpdklab
2025-04-09 2:49 ` dpdklab
2025-04-09 2:53 ` dpdklab
2025-04-09 3:03 ` dpdklab
2025-04-09 3:07 ` dpdklab
2025-04-09 3:10 ` |PENDING| " dpdklab
2025-04-09 3:34 ` |SUCCESS| " dpdklab
2025-04-09 3:40 ` |WARNING| " dpdklab
2025-04-09 3:43 ` |SUCCESS| " dpdklab
2025-04-09 3:59 ` |PENDING| " dpdklab
2025-04-09 4:31 ` |SUCCESS| " dpdklab
2025-04-09 4:35 ` dpdklab
2025-04-09 4:43 ` |WARNING| " dpdklab
2025-04-09 5:03 ` |SUCCESS| " dpdklab
2025-04-09 5:14 ` dpdklab
2025-04-09 6:17 ` dpdklab
2025-04-09 7:01 ` dpdklab
2025-04-09 10:27 ` dpdklab
2025-04-10 22:58 ` dpdklab
2025-04-10 23:01 ` 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=20250408224339.1407908-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=longli@linuxonhyperv.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).