automatic DPDK test reports
 help / color / mirror / Atom feed
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| pw99869 [dpdk-dev] [PATCH v7 9/9] app/bbdev: add test vectors for transport blocks
Date: Tue, 28 Sep 2021 05:38:38 -0400	[thread overview]
Message-ID: <20210928093838.24330-1-robot@bytheb.org> (raw)
In-Reply-To: <20210928082953.18731-10-nipun.gupta@nxp.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=pw|patchwork.dpdk.org|build|19215|SHA|363b1d640f9e0a16b784a8b4f4a3087cfb189ab9|passed|https://github.com/ovsrobot/dpdk/actions/runs/1281850193|[dpdk-dev] [PATCH v2] net/virtio: fix virtio-user init when using existing tap|ovsrobot/dpdk|build, Size: 2690 bytes --]

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/1281846092
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/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: In function ‘parse_u16_arg’:
../drivers/baseband/la12xx/bbdev_la12xx.c:910:22: error: format ‘%llu’ expects argument of type ‘long long unsigned int’, but argument 4 has type ‘long unsigned int’ [-Werror=format=]
   rte_bbdev_log(ERR, "Invalid value %" PRIu64 " for %s",
                      ^
../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:105:34: note: format string is defined here
 # define PRIu64  __PRI64_PREFIX "u"
cc1: all warnings being treated as errors
[1807/2521] Compiling C object 'drivers/a715181@@tmp_rte_baseband_turbo_sw@sta/baseband_turbo_sw_bbdev_turbo_software.c.o'.
[1808/2521] 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-----------------------------

      parent reply	other threads:[~2021-09-28  9:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210928082953.18731-10-nipun.gupta@nxp.com>
2021-09-28  8:40 ` [dpdk-test-report] |SUCCESS| pw99869 " checkpatch
2021-09-28  9:38 ` 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=20210928093838.24330-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).