From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: ktejasree@marvell.com, robot@bytheb.org
Subject: |FAILURE| pw153662 [PATCH 40/40] crypto/cnxk: copy 8B iv into sess in aes ctr
Date: Fri, 23 May 2025 11:03:35 -0400 [thread overview]
Message-ID: <20250523150335.1507937-1-robot@bytheb.org> (raw)
In-Reply-To: <20250523135111.2178408-41-ktejasree@marvell.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/153662/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/15212194583
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
####################################################################################
rte_atomic_load_explicit(&infl_req->res.u64[0], rte_memory_order_relaxed);
^ ~~~~~~~~~~~~~~~~~~~~~
../lib/eal/include/rte_stdatomic.h:69:2: note: expanded from macro 'rte_atomic_load_explicit'
atomic_load_explicit(ptr, memorder)
^ ~~~
/usr/lib/llvm-14/lib/clang/14.0.0/include/stdatomic.h:130:30: note: expanded from macro 'atomic_load_explicit'
#define atomic_load_explicit __c11_atomic_load
^
../drivers/crypto/cnxk/cn20k_cryptodev_ops.c:980:15: error: address argument to atomic operation must be a pointer to _Atomic type ('uint64_t *' (aka 'unsigned long *') invalid)
res.u64[0] = rte_atomic_load_explicit(&infl_req->res.u64[0], rte_memory_order_relaxed);
^ ~~~~~~~~~~~~~~~~~~~~~
../lib/eal/include/rte_stdatomic.h:69:2: note: expanded from macro 'rte_atomic_load_explicit'
atomic_load_explicit(ptr, memorder)
^ ~~~
/usr/lib/llvm-14/lib/clang/14.0.0/include/stdatomic.h:130:30: note: expanded from macro 'atomic_load_explicit'
#define atomic_load_explicit __c11_atomic_load
^
8 errors generated.
[617/3552] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn20k_ipsec.c.o
[618/3552] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn20k_tls.c.o
[619/3552] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cnxk_cryptodev.c.o
[620/3552] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn9k_cryptodev_ops.c.o
[621/3552] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn10k_cryptodev_ops.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-05-23 15:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250523135111.2178408-41-ktejasree@marvell.com>
2025-05-23 13:24 ` |SUCCESS| pw153626-153662 " qemudev
2025-05-23 13:29 ` qemudev
2025-05-23 13:59 ` |SUCCESS| pw153662 " checkpatch
2025-05-23 14:34 ` |SUCCESS| pw153626-153662 [PATCH] [40/40] crypto/cnxk: copy 8B iv in dpdklab
2025-05-23 14:40 ` |PENDING| " dpdklab
2025-05-23 14:44 ` dpdklab
2025-05-23 14:46 ` |SUCCESS| " dpdklab
2025-05-23 14:48 ` dpdklab
2025-05-23 14:48 ` |PENDING| " dpdklab
2025-05-23 14:49 ` dpdklab
2025-05-23 14:50 ` |SUCCESS| " dpdklab
2025-05-23 15:00 ` dpdklab
2025-05-23 15:01 ` |PENDING| " dpdklab
2025-05-23 15:03 ` 0-day Robot [this message]
2025-05-23 15:14 ` |SUCCESS| " dpdklab
2025-05-23 15:28 ` |PENDING| " dpdklab
2025-05-23 15:38 ` |SUCCESS| " dpdklab
2025-05-23 15:41 ` |WARNING| " dpdklab
2025-05-23 15:42 ` dpdklab
2025-05-23 15:53 ` |SUCCESS| " dpdklab
2025-05-23 15:56 ` |WARNING| " dpdklab
2025-05-23 15:56 ` |SUCCESS| " dpdklab
2025-05-23 16:16 ` dpdklab
2025-05-23 18:25 ` dpdklab
2025-05-23 19:21 ` 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=20250523150335.1507937-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=ktejasree@marvell.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).