automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: skori@marvell.com, robot@bytheb.org
Subject: |FAILURE| pw131265 [PATCH v3 1/1] app/graph: add example for different usecases
Date: Fri,  8 Sep 2023 07:39:40 -0400	[thread overview]
Message-ID: <20230908113940.1644839-1-robot@bytheb.org> (raw)
In-Reply-To: <20230908104907.4060511-1-skori@marvell.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/131265/

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/6120902336
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-shared-aarch64" failed at step Build and test
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-shared-aarch64" at step Build and test
####################################################################################
[2571/3996] Compiling C object 'app/a172ced@@dpdk-graph@exe/graph_neigh.c.o'.
[2572/3996] Compiling C object 'app/a172ced@@dpdk-graph@exe/graph_l3fwd.c.o'.
FAILED: app/a172ced@@dpdk-graph@exe/graph_l3fwd.c.o 
ccache aarch64-linux-gnu-gcc -Iapp/a172ced@@dpdk-graph@exe -Iapp -I../app -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/arm/include -I../lib/eal/arm/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/graph -I../lib/graph -Ilib/pcapng -I../lib/pcapng -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/lpm -I../lib/lpm -Ilib/hash -I../lib/hash -Ilib/rcu -I../lib/rcu -Ilib/node -I../lib/node -Ilib/cryptodev -I../lib/cryptodev -fdiagnostics-color=always -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-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -march=armv8-a+crc -moutline-atomics -DALLOW_EXPERIMENTAL_API -MD -MQ 'app/a172ced@@dpdk-graph@exe/graph_l3fwd.c.o' -MF 'app/a172ced@@dpdk-graph@exe/graph_l3fwd.c.o.d' -o 'app/a172ced@@dpdk-graph@exe/graph_l3fwd.c.o' -c ../app/graph/l3fwd.c
../app/graph/l3fwd.c: In function ‘l3fwd_pattern_configure’:
../app/graph/l3fwd.c:58:30: error: comparison is always true due to limited range of data type [-Werror=type-limits]
   58 |  for (lcore_id = 0; lcore_id < RTE_MAX_LCORE; lcore_id++) {
      |                              ^
In file included from ../lib/eal/include/generic/rte_spinlock.h:20,
                 from ../lib/eal/arm/include/rte_spinlock.h:17,
                 from ../lib/eal/include/generic/rte_power_intrinsics.h:11,
                 from ../lib/eal/arm/include/rte_power_intrinsics.h:14,
                 from ../lib/ethdev/rte_ethdev.h:173,
                 from ../app/graph/l3fwd.c:13:
../lib/eal/include/rte_lcore.h:227:9: error: comparison is always true due to limited range of data type [-Werror=type-limits]
  227 |       i < RTE_MAX_LCORE;      \
      |         ^
../app/graph/l3fwd.c:123:2: note: in expansion of macro ‘RTE_LCORE_FOREACH_WORKER’
  123 |  RTE_LCORE_FOREACH_WORKER(lcore_id) {
      |  ^~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
[2573/3996] Compiling C object 'app/a172ced@@dpdk-graph@exe/graph_utils.c.o'.
[2574/3996] Compiling C object 'drivers/a715181@@tmp_rte_event_cnxk@sta/event_cnxk_deq_cn10k_deq_112_127_tmo_seg.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-shared-aarch64" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2023-09-08 11:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230908104907.4060511-1-skori@marvell.com>
2023-09-08 10:50 ` |WARNING| " checkpatch
2023-09-08 11:39 ` 0-day Robot [this message]
2023-09-12 13:11 ` |SUCCESS| " qemudev
2023-09-12 13:15 ` qemudev

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=20230908113940.1644839-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=skori@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).