From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: stephen@networkplumber.org, robot@bytheb.org
Subject: |FAILURE| pw139190 [RFC] latencystats: performance overhaul
Date: Mon, 8 Apr 2024 16:44:15 -0400 [thread overview]
Message-ID: <20240408204415.816708-1-robot@bytheb.org> (raw)
In-Reply-To: <20240408195036.182545-1-stephen@networkplumber.org>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/139190/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8605948264
Build Logs:
-----------------------Summary of failed steps-----------------------
"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-stdatomic" at step Build and test
####################################################################################
| ~~~~~~~~~~~~~~~~^~~~~~~~
../lib/latencystats/rte_latencystats.c:118:64: error: passing argument 1 of ‘latencystat_read_ns’ from incompatible pointer type [-Werror=incompatible-pointer-types]
118 | sum.avg_latency += latencystat_read_ns(&stats->avg_latency);
| ^~~~~~~~~~~~~~~~~~~
| |
| _Atomic const uint64_t * {aka _Atomic const long unsigned int *}
../lib/latencystats/rte_latencystats.c:80:37: note: expected ‘const uint64_t *’ {aka ‘const long unsigned int *’} but argument is of type ‘_Atomic const uint64_t *’ {aka ‘_Atomic const long unsigned int *’}
80 | latencystat_read_ns(const uint64_t *stat_ptr)
| ~~~~~~~~~~~~~~~~^~~~~~~~
../lib/latencystats/rte_latencystats.c:119:59: error: passing argument 1 of ‘latencystat_read_ns’ from incompatible pointer type [-Werror=incompatible-pointer-types]
119 | sum.jitter += latencystat_read_ns(&stats->jitter);
| ^~~~~~~~~~~~~~
| |
| _Atomic const uint64_t * {aka _Atomic const long unsigned int *}
../lib/latencystats/rte_latencystats.c:80:37: note: expected ‘const uint64_t *’ {aka ‘const long unsigned int *’} but argument is of type ‘_Atomic const uint64_t *’ {aka ‘_Atomic const long unsigned int *’}
80 | latencystat_read_ns(const uint64_t *stat_ptr)
| ~~~~~~~~~~~~~~~~^~~~~~~~
cc1: all warnings being treated as errors
[321/2954] Generating jobstats.sym_chk with a meson_exe.py custom command.
[322/2954] Generating ip_frag.sym_chk with a meson_exe.py custom command.
[323/2954] Compiling C object 'lib/76b5a35@@rte_lpm@sta/lpm_rte_lpm.c.o'.
[324/2954] Compiling C object 'lib/76b5a35@@rte_lpm@sta/lpm_rte_lpm6.c.o'.
[325/2954] Generating eventdev.sym_chk with a meson_exe.py custom command.
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
####################################################################################
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
objdump: Warning: Unrecognized form: 0x22
[326/2954] Compiling C object 'lib/member/52c0277@@sketch_avx512_tmp@sta/rte_member_sketch_avx512.c.o'.
[327/2954] Compiling C object 'lib/76b5a35@@rte_lpm@sta/lpm_rte_lpm6.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-04-08 20:44 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240408195036.182545-1-stephen@networkplumber.org>
2024-04-08 19:27 ` |SUCCESS| " qemudev
2024-04-08 19:31 ` qemudev
2024-04-08 19:52 ` |WARNING| " checkpatch
2024-04-08 20:29 ` |SUCCESS| pw139190 [PATCH] " dpdklab
2024-04-08 20:29 ` dpdklab
2024-04-08 20:29 ` dpdklab
2024-04-08 20:30 ` dpdklab
2024-04-08 20:30 ` dpdklab
2024-04-08 20:30 ` dpdklab
2024-04-08 20:31 ` dpdklab
2024-04-08 20:31 ` dpdklab
2024-04-08 20:31 ` dpdklab
2024-04-08 20:31 ` dpdklab
2024-04-08 20:32 ` dpdklab
2024-04-08 20:32 ` dpdklab
2024-04-08 20:32 ` dpdklab
2024-04-08 20:33 ` dpdklab
2024-04-08 20:33 ` dpdklab
2024-04-08 20:33 ` dpdklab
2024-04-08 20:33 ` dpdklab
2024-04-08 20:33 ` dpdklab
2024-04-08 20:33 ` dpdklab
2024-04-08 20:33 ` dpdklab
2024-04-08 20:33 ` dpdklab
2024-04-08 20:34 ` dpdklab
2024-04-08 20:34 ` dpdklab
2024-04-08 20:34 ` dpdklab
2024-04-08 20:35 ` dpdklab
2024-04-08 20:35 ` dpdklab
2024-04-08 20:35 ` dpdklab
2024-04-08 20:35 ` dpdklab
2024-04-08 20:35 ` dpdklab
2024-04-08 20:36 ` dpdklab
2024-04-08 20:36 ` dpdklab
2024-04-08 20:36 ` dpdklab
2024-04-08 20:36 ` dpdklab
2024-04-08 20:36 ` dpdklab
2024-04-08 20:37 ` dpdklab
2024-04-08 20:37 ` dpdklab
2024-04-08 20:37 ` dpdklab
2024-04-08 20:37 ` dpdklab
2024-04-08 20:37 ` dpdklab
2024-04-08 20:37 ` dpdklab
2024-04-08 20:38 ` dpdklab
2024-04-08 20:38 ` dpdklab
2024-04-08 20:38 ` dpdklab
2024-04-08 20:38 ` dpdklab
2024-04-08 20:38 ` dpdklab
2024-04-08 20:39 ` dpdklab
2024-04-08 20:39 ` dpdklab
2024-04-08 20:39 ` dpdklab
2024-04-08 20:39 ` dpdklab
2024-04-08 20:40 ` dpdklab
2024-04-08 20:40 ` dpdklab
2024-04-08 20:40 ` dpdklab
2024-04-08 20:40 ` dpdklab
2024-04-08 20:40 ` dpdklab
2024-04-08 20:41 ` dpdklab
2024-04-08 20:41 ` dpdklab
2024-04-08 20:41 ` dpdklab
2024-04-08 20:42 ` dpdklab
2024-04-08 20:42 ` dpdklab
2024-04-08 20:42 ` dpdklab
2024-04-08 20:42 ` dpdklab
2024-04-08 20:43 ` dpdklab
2024-04-08 20:43 ` dpdklab
2024-04-08 20:43 ` dpdklab
2024-04-08 20:43 ` dpdklab
2024-04-08 20:43 ` dpdklab
2024-04-08 20:43 ` dpdklab
2024-04-08 20:44 ` dpdklab
2024-04-08 20:44 ` 0-day Robot [this message]
2024-04-08 20:45 ` dpdklab
2024-04-08 20:46 ` dpdklab
2024-04-08 20:47 ` dpdklab
2024-04-08 20:47 ` dpdklab
2024-04-08 20:47 ` dpdklab
2024-04-08 20:48 ` dpdklab
2024-04-08 20:51 ` dpdklab
2024-04-08 20:51 ` dpdklab
2024-04-08 20:51 ` dpdklab
2024-04-08 20:52 ` dpdklab
2024-04-08 20:55 ` dpdklab
2024-04-08 20:55 ` dpdklab
2024-04-08 20:59 ` dpdklab
2024-04-08 21:13 ` dpdklab
2024-04-08 21:26 ` dpdklab
2024-04-08 21:29 ` dpdklab
2024-04-08 21:44 ` 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=20240408204415.816708-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=stephen@networkplumber.org \
--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).