automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: hemant.agrawal@nxp.com, robot@bytheb.org
Subject: [dpdk-test-report] |FAILURE| pw92108 [dpdk-dev] [PATCH v4 8/8] app/bbdev: add test vectors for transport blocks
Date: Sat, 24 Apr 2021 07:58:10 -0400	[thread overview]
Message-ID: <20210424115810.2679-1-robot@bytheb.org> (raw)
In-Reply-To: <20210424103700.8098-9-hemant.agrawal@nxp.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/780365633
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"
####################################################################################
    "ipc_metadata_t =%lx, mhif->ipc_regs.ipc_mdata_size=%x",
    ^
../drivers/baseband/la12xx/bbdev_la12xx_pmd_logs.h:9:51: note: in definition of macro ‘rte_bbdev_log’
  rte_log(RTE_LOG_ ## level, bbdev_la12xx_logtype, fmt "\n", \
                                                   ^~~
../drivers/baseband/la12xx/bbdev_la12xx.c:871:23: note: format string is defined here
    "ipc_metadata_t =%lx, mhif->ipc_regs.ipc_mdata_size=%x",
                     ~~^
                     %x
In file included from ../drivers/baseband/la12xx/bbdev_la12xx.c:21:0:
../drivers/baseband/la12xx/bbdev_la12xx.c:875:22: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘unsigned int’ [-Werror=format=]
   rte_bbdev_log(ERR, "gul_hif size=%lx", sizeof(struct gul_hif));
                      ^
../drivers/baseband/la12xx/bbdev_la12xx_pmd_logs.h:9:51: note: in definition of macro ‘rte_bbdev_log’
  rte_log(RTE_LOG_ ## level, bbdev_la12xx_logtype, fmt "\n", \
                                                   ^~~
../drivers/baseband/la12xx/bbdev_la12xx.c:875:38: note: format string is defined here
   rte_bbdev_log(ERR, "gul_hif size=%lx", sizeof(struct gul_hif));
                                    ~~^
                                    %x
cc1: all warnings being treated as errors
[1808/2517] Compiling C object 'drivers/a715181@@tmp_rte_baseband_turbo_sw@sta/baseband_turbo_sw_bbdev_turbo_software.c.o'.
[1809/2517] 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-04-24 11:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210424103700.8098-9-hemant.agrawal@nxp.com>
2021-04-24 10:40 ` [dpdk-test-report] |SUCCESS| pw92108 " checkpatch
2021-04-24 11:58 ` 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=20210424115810.2679-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=hemant.agrawal@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).