From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: pbhagavatula@marvell.com, robot@bytheb.org
Subject: |FAILURE| pw115791 [PATCH v2 5/5] examples/l3fwd: use em vector path for event vector
Date: Fri, 2 Sep 2022 06:40:03 -0400 [thread overview]
Message-ID: <20220902104003.7061-1-robot@bytheb.org> (raw)
In-Reply-To: <20220902091833.9074-5-pbhagavatula@marvell.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/115791/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/2978096651
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-shared-riscv64" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-shared-riscv64" at step Build and test
####################################################################################
[3021/4059] Linking target examples/dpdk-ipsec-secgw.
[3022/4059] Compiling C object 'examples/c590b3c@@dpdk-l3fwd@exe/l3fwd_l3fwd_em.c.o'.
[3023/4059] Compiling C object 'examples/c590b3c@@dpdk-l3fwd@exe/l3fwd_l3fwd_lpm.c.o'.
[3024/4059] Compiling C object 'examples/c590b3c@@dpdk-l3fwd@exe/l3fwd_l3fwd_event_generic.c.o'.
[3025/4059] Compiling C object 'examples/c590b3c@@dpdk-l3fwd@exe/l3fwd_l3fwd_event.c.o'.
[3026/4059] Compiling C object 'examples/c590b3c@@dpdk-l3fwd@exe/l3fwd_l3fwd_event_internal_port.c.o'.
[3027/4059] Compiling C object 'examples/c590b3c@@dpdk-l3fwd-graph@exe/l3fwd-graph_main.c.o'.
[3028/4059] Compiling C object 'examples/c590b3c@@dpdk-l3fwd-power@exe/l3fwd-power_main.c.o'.
[3029/4059] Compiling C object 'examples/c590b3c@@dpdk-l3fwd-power@exe/l3fwd-power_perf_core.c.o'.
[3030/4059] Linking target examples/dpdk-l3fwd-graph.
[3031/4059] Compiling C object 'examples/c590b3c@@dpdk-l3fwd@exe/l3fwd_l3fwd_fib.c.o'.
FAILED: examples/c590b3c@@dpdk-l3fwd@exe/l3fwd_l3fwd_fib.c.o
ccache riscv64-linux-gnu-gcc -Iexamples/c590b3c@@dpdk-l3fwd@exe -Iexamples -I../examples -Iexamples/l3fwd -I../examples/l3fwd -I../examples/common -I. -I../ -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/riscv/include -I../lib/eal/riscv/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/telemetry/../metrics -I../lib/telemetry/../metrics -Ilib/telemetry -I../lib/telemetry -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/ethdev -I../lib/ethdev -Ilib/meter -I../lib/meter -Ilib/cmdline -I../lib/cmdline -Ilib/acl -I../lib/acl -Ilib/hash -I../lib/hash -Ilib/rcu -I../lib/rcu -Ilib/lpm -I../lib/lpm -Ilib/fib -I../lib/fib -Ilib/rib -I../lib/rib -Ilib/eventdev -I../lib/eventdev -Ilib/timer -I../lib/timer -Ilib/cryptodev -I../lib/cryptodev -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -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-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -march=rv64gc -Wno-format-truncation -DALLOW_EXPERIMENTAL_API -MD -MQ 'examples/c590b3c@@dpdk-l3fwd@exe/l3fwd_l3fwd_fib.c.o' -MF 'examples/c590b3c@@dpdk-l3fwd@exe/l3fwd_l3fwd_fib.c.o.d' -o 'examples/c590b3c@@dpdk-l3fwd@exe/l3fwd_l3fwd_fib.c.o' -c ../examples/l3fwd/l3fwd_fib.c
../examples/l3fwd/l3fwd_fib.c: In function ‘process_packet’:
../examples/l3fwd/l3fwd_fib.c:86:2: error: too many arguments to function ‘rfc1812_process’
86 | rfc1812_process(
| ^~~~~~~~~~~~~~~
In file included from ../examples/l3fwd/l3fwd_fib.c:22:
../examples/l3fwd/l3fwd_common.h:33:1: note: declared here
33 | rfc1812_process(struct rte_ipv4_hdr *ipv4_hdr, uint16_t *dp, uint32_t ptype)
| ^~~~~~~~~~~~~~~
[3032/4059] Compiling C object 'examples/c590b3c@@dpdk-l3fwd@exe/l3fwd_main.c.o'.
[3033/4059] Generating rte_event_cnxk.pmd.c with a custom command.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-shared-riscv64" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2022-09-02 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220902091833.9074-5-pbhagavatula@marvell.com>
2022-09-02 9:20 ` |SUCCESS| " checkpatch
2022-09-02 10:40 ` 0-day Robot [this message]
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=20220902104003.7061-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=pbhagavatula@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).