From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: nipun.gupta@nxp.com, robot@bytheb.org
Subject: [dpdk-test-report] |FAILURE| pw100612 [dpdk-dev] [PATCH v8 8/8] app/bbdev: handle endianness of test data
Date: Wed, 6 Oct 2021 09:20:52 -0400 [thread overview]
Message-ID: <20211006132052.26540-1-robot@bytheb.org> (raw)
In-Reply-To: <20211006113112.11163-9-nipun.gupta@nxp.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/100612/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/1311891676
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-18.04-gcc-static-i386" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-18.04-gcc-static-i386" at step Build and test
####################################################################################
from ../lib/mbuf/rte_mbuf.h:38,
from ../lib/bbdev/rte_bbdev_op.h:24,
from ../lib/bbdev/rte_bbdev.h:40,
from ../drivers/baseband/la12xx/bbdev_la12xx.c:18:
/usr/include/inttypes.h:121:34: note: format string is defined here
# define PRIx64 __PRI64_PREFIX "x"
In file included from ../drivers/baseband/la12xx/bbdev_la12xx.c:21:0:
../drivers/baseband/la12xx/bbdev_la12xx.c:873:22: error: format ‘%llx’ expects argument of type ‘long long unsigned int’, but argument 4 has type ‘unsigned int’ [-Werror=format=]
rte_bbdev_log(ERR, "gul_hif size=0x%" PRIx64,
^
../drivers/baseband/la12xx/bbdev_la12xx_pmd_logs.h:11:51: note: in definition of macro ‘rte_bbdev_log’
rte_log(RTE_LOG_ ## level, bbdev_la12xx_logtype, fmt "\n", \
^~~
In file included from ../lib/mempool/rte_mempool.h:40:0,
from ../lib/mbuf/rte_mbuf.h:38,
from ../lib/bbdev/rte_bbdev_op.h:24,
from ../lib/bbdev/rte_bbdev.h:40,
from ../drivers/baseband/la12xx/bbdev_la12xx.c:18:
/usr/include/inttypes.h:121:34: note: format string is defined here
# define PRIx64 __PRI64_PREFIX "x"
cc1: all warnings being treated as errors
[1818/2534] Generating rte_baseband_turbo_sw.pmd.c with a custom command.
[1819/2534] Compiling C object 'app/a172ced@@dpdk-pdump@exe/pdump_main.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-18.04-gcc-static-i386" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2021-10-06 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211006113112.11163-9-nipun.gupta@nxp.com>
2021-10-06 11:33 ` [dpdk-test-report] |SUCCESS| pw100612 " checkpatch
2021-10-06 13:20 ` 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=20211006132052.26540-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=nipun.gupta@nxp.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).