From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: konstantin.ananyev@huawei.com, robot@bytheb.org
Subject: |FAILURE| pw148301 [PATCH v9 7/7] test: add stress test suite
Date: Mon, 11 Nov 2024 07:25:34 -0500 [thread overview]
Message-ID: <20241111122534.3423887-1-robot@bytheb.org> (raw)
In-Reply-To: <20241111122535.6214-8-konstantin.ananyev@huawei.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/148301/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/11777907834
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
####################################################################################
^ ~~~~~~~~
../lib/eal/include/rte_stdatomic.h:72: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
^
In file included from ../app/test/test_soring_mt_stress.c:5:
../app/test/test_soring_stress_impl.h:562:2: error: address argument to atomic operation must be a pointer to _Atomic type ('uint32_t *' (aka 'unsigned int *') invalid)
rte_atomic_store_explicit(&wrk_cmd, WRK_CMD_STOP,
^ ~~~~~~~~
../lib/eal/include/rte_stdatomic.h:72: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
^
4 errors generated.
[3081/3120] Compiling C object app/dpdk-test.p/test_test_table_acl.c.o
[3082/3120] Compiling C object app/dpdk-test.p/test_test_stack.c.o
[3083/3120] Compiling C object app/dpdk-test.p/test_test_memcpy_perf.c.o
[3084/3120] Compiling C object app/dpdk-test.p/test_test_ring.c.o
[3085/3120] Compiling C object app/dpdk-test.p/test_test_ring_perf.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-11-11 12:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241111122535.6214-8-konstantin.ananyev@huawei.com>
2024-11-11 11:13 ` |SUCCESS| pw148296-148301 " qemudev
2024-11-11 11:17 ` qemudev
2024-11-11 11:36 ` |WARNING| pw148301 " checkpatch
2024-11-11 12:25 ` 0-day Robot [this message]
2024-11-11 13:21 ` |SUCCESS| pw148296-148301 [PATCH] [v9,7/7] test: add stress test sui dpdklab
2024-11-11 13:47 ` dpdklab
2024-11-11 13:50 ` dpdklab
2024-11-11 13:56 ` dpdklab
2024-11-11 14:04 ` dpdklab
2024-11-11 14:13 ` dpdklab
2024-11-11 15:37 ` |PENDING| " dpdklab
2024-11-11 15:40 ` |SUCCESS| " dpdklab
2024-11-11 15:56 ` |PENDING| " dpdklab
2024-11-11 16:00 ` |SUCCESS| " dpdklab
2024-11-11 16:16 ` dpdklab
2024-11-11 16:18 ` dpdklab
2024-11-11 16:43 ` |PENDING| " dpdklab
2024-11-11 16:45 ` |SUCCESS| " dpdklab
2024-11-11 17:41 ` dpdklab
2024-11-11 17:42 ` |WARNING| " dpdklab
2024-11-11 18:15 ` dpdklab
2024-11-11 18:58 ` |SUCCESS| " dpdklab
2024-11-11 20:17 ` |WARNING| " dpdklab
2024-11-11 20:32 ` dpdklab
2024-11-11 20:56 ` |SUCCESS| " dpdklab
2024-11-11 22:33 ` 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=20241111122534.3423887-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=konstantin.ananyev@huawei.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).