From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: chaoyong.he@corigine.com, robot@bytheb.org
Subject: |FAILURE| pw141152 [PATCH v2 11/11] doc: update nfp document
Date: Fri, 14 Jun 2024 04:06:04 -0400 [thread overview]
Message-ID: <20240614080604.688332-1-robot@bytheb.org> (raw)
In-Reply-To: <20240614070120.2663160-12-chaoyong.he@corigine.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/141152/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9512315065
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-clang-stdatomic" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-stdatomic" at step Build and test
####################################################################################
[2453/2956] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_mlx5@sta/vdpa_mlx5_mlx5_vdpa_virtq.c.o'.
[2454/2956] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_mlx5@sta/vdpa_mlx5_mlx5_vdpa.c.o'.
[2455/2956] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_nfp@sta/vdpa_nfp_nfp_vdpa_log.c.o'.
[2456/2956] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_mlx5@sta/vdpa_mlx5_mlx5_vdpa_steer.c.o'.
[2457/2956] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_mlx5@sta/vdpa_mlx5_mlx5_vdpa_lm.c.o'.
[2458/2956] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_nfp@sta/vdpa_nfp_nfp_vdpa.c.o'.
FAILED: drivers/a715181@@tmp_rte_vdpa_nfp@sta/vdpa_nfp_nfp_vdpa.c.o
ccache clang -Idrivers/a715181@@tmp_rte_vdpa_nfp@sta -Idrivers -I../drivers -Idrivers/vdpa/nfp -I../drivers/vdpa/nfp -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/log -I../lib/log -Ilib/telemetry/../metrics -I../lib/telemetry/../metrics -Ilib/telemetry -I../lib/telemetry -Ilib/pci -I../lib/pci -Ilib/vhost -I../lib/vhost -Ilib/ethdev -I../lib/ethdev -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 -Ilib/cryptodev -I../lib/cryptodev -Ilib/rcu -I../lib/rcu -Ilib/hash -I../lib/hash -Ilib/dmadev -I../lib/dmadev -Idrivers/common/nfp -I../drivers/common/nfp -Xclang -fcolor-diagnostics -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O2 -g -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-address-of-packed-member -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=corei7 -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -DRTE_LOG_DEFAULT_LOGTYPE=pmd.vdpa.nfp -DRTE_ANNOTATE_LOCKS -Wthread-safety -MD -MQ 'drivers/a715181@@tmp_rte_vdpa_nfp@sta/vdpa_nfp_nfp_vdpa.c.o' -MF 'drivers/a715181@@tmp_rte_vdpa_nfp@sta/vdpa_nfp_nfp_vdpa.c.o.d' -o 'drivers/a715181@@tmp_rte_vdpa_nfp@sta/vdpa_nfp_nfp_vdpa.c.o' -c ../drivers/vdpa/nfp/nfp_vdpa.c
../drivers/vdpa/nfp/nfp_vdpa.c:470:4: error: address argument to atomic operation must be a pointer to _Atomic type ('__virtio16 *' (aka 'unsigned short *') invalid)
rte_atomic_store_explicit(&vring.used->idx, vring.avail->idx,
^ ~~~~~~~~~~~~~~~~
../lib/eal/include/rte_stdatomic.h:76:2: note: expanded from macro 'rte_atomic_store_explicit'
atomic_store_explicit(ptr, val, memorder)
^ ~~~
/usr/lib/llvm-14/lib/clang/14.0.0/include/stdatomic.h:127:31: note: expanded from macro 'atomic_store_explicit'
#define atomic_store_explicit __c11_atomic_store
^
1 error generated.
[2459/2956] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_sfc@sta/vdpa_sfc_sfc_vdpa.c.o'.
[2460/2956] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_nfp@sta/vdpa_nfp_nfp_vdpa_core.c.o'.
[2461/2956] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_mlx5@sta/vdpa_mlx5_mlx5_vdpa_cthread.c.o'.
[2462/2956] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_sfc@sta/vdpa_sfc_sfc_vdpa_mcdi.c.o'.
[2463/2956] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_sfc@sta/vdpa_sfc_sfc_vdpa_hw.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:[~2024-06-14 8:06 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240614070120.2663160-12-chaoyong.he@corigine.com>
2024-06-14 6:43 ` |SUCCESS| pw141142-141152 " qemudev
2024-06-14 6:48 ` qemudev
2024-06-14 7:04 ` |SUCCESS| pw141152 " checkpatch
2024-06-14 8:06 ` 0-day Robot [this message]
2024-06-14 9:19 ` |SUCCESS| pw141142-141152 [PATCH] [v2,11/11] doc: update nfp documen dpdklab
2024-06-14 9:50 ` dpdklab
2024-06-14 10:05 ` dpdklab
2024-06-14 10:09 ` dpdklab
2024-06-14 10:12 ` dpdklab
2024-06-14 10:13 ` dpdklab
2024-06-14 10:14 ` dpdklab
2024-06-14 10:15 ` dpdklab
2024-06-14 10:17 ` dpdklab
2024-06-14 10:21 ` dpdklab
2024-06-14 10:26 ` dpdklab
2024-06-14 10:27 ` dpdklab
2024-06-14 10:27 ` dpdklab
2024-06-14 10:27 ` dpdklab
2024-06-14 10:28 ` dpdklab
2024-06-14 10:35 ` dpdklab
2024-06-14 10:35 ` dpdklab
2024-06-14 10:36 ` dpdklab
2024-06-14 10:37 ` dpdklab
2024-06-14 10:38 ` dpdklab
2024-06-14 10:39 ` dpdklab
2024-06-14 10:41 ` dpdklab
2024-06-14 10:56 ` dpdklab
2024-06-14 11:04 ` dpdklab
2024-06-14 11:18 ` dpdklab
2024-06-14 11:35 ` dpdklab
2024-06-14 11:36 ` dpdklab
2024-06-14 11:36 ` dpdklab
2024-06-14 11:37 ` dpdklab
2024-06-14 11:38 ` dpdklab
2024-06-14 11:38 ` dpdklab
2024-06-14 11:38 ` dpdklab
2024-06-14 11:39 ` dpdklab
2024-06-14 11:39 ` dpdklab
2024-06-14 11:40 ` dpdklab
2024-06-14 11:41 ` dpdklab
2024-06-14 11:48 ` dpdklab
2024-06-14 11:48 ` dpdklab
2024-06-14 11:49 ` dpdklab
2024-06-14 11:52 ` dpdklab
2024-06-14 11:55 ` dpdklab
2024-06-14 11:56 ` dpdklab
2024-06-14 11:57 ` dpdklab
2024-06-14 11:57 ` dpdklab
2024-06-14 11:57 ` dpdklab
2024-06-14 11:59 ` dpdklab
2024-06-14 11:59 ` dpdklab
2024-06-14 11:59 ` dpdklab
2024-06-14 12:00 ` dpdklab
2024-06-14 12:00 ` dpdklab
2024-06-14 12:01 ` dpdklab
2024-06-14 12:01 ` dpdklab
2024-06-14 12:01 ` dpdklab
2024-06-14 12:02 ` dpdklab
2024-06-14 12:02 ` dpdklab
2024-06-14 12:02 ` dpdklab
2024-06-14 12:03 ` dpdklab
2024-06-14 12:06 ` dpdklab
2024-06-14 12:07 ` dpdklab
2024-06-14 12:07 ` dpdklab
2024-06-14 12:09 ` dpdklab
2024-06-14 12:09 ` dpdklab
2024-06-14 12:09 ` dpdklab
2024-06-14 12:10 ` dpdklab
2024-06-14 12:27 ` dpdklab
2024-06-14 12:27 ` dpdklab
2024-06-14 12:28 ` dpdklab
2024-06-14 12:28 ` dpdklab
2024-06-14 12:28 ` dpdklab
2024-06-14 12:28 ` dpdklab
2024-06-14 12:29 ` dpdklab
2024-06-14 12:37 ` dpdklab
2024-06-14 12:40 ` dpdklab
2024-06-14 12:46 ` dpdklab
2024-06-14 12:48 ` dpdklab
2024-06-14 12:48 ` dpdklab
2024-06-14 12:52 ` dpdklab
2024-06-14 12:55 ` dpdklab
2024-06-14 12:56 ` dpdklab
2024-06-14 12:57 ` dpdklab
2024-06-14 12:57 ` dpdklab
2024-06-14 12:57 ` dpdklab
2024-06-14 12:57 ` dpdklab
2024-06-14 12:58 ` dpdklab
2024-06-14 13:24 ` dpdklab
2024-06-14 13:28 ` dpdklab
2024-06-14 13:29 ` dpdklab
2024-06-14 13:33 ` dpdklab
2024-06-14 14:07 ` dpdklab
2024-06-14 14:13 ` dpdklab
2024-06-14 14:14 ` dpdklab
2024-06-14 14:17 ` dpdklab
2024-06-14 14:17 ` dpdklab
2024-06-14 14:17 ` dpdklab
2024-06-14 14:34 ` 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=20240614080604.688332-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=chaoyong.he@corigine.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).