automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: fengchengwen@huawei.com, robot@bytheb.org
Subject: [dpdk-test-report] |FAILURE| pw103265 [dpdk-dev] [PATCH 6/6] devbind: add Kunpeng DMA to dmadev category
Date: Sat, 30 Oct 2021 07:39:18 -0400	[thread overview]
Message-ID: <20211030113918.12198-1-robot@bytheb.org> (raw)
In-Reply-To: <20211030103619.29924-7-fengchengwen@huawei.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/1402149377
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
####################################################################################
   (((~0UL) << (l)) & (~0UL >> (BITS_PER_LONG - 1 - (h))))
                            ^
../drivers/dma/hisilicon/hisi_dmadev.h:15:36: note: in definition of macro ‘BF_SHF’
 #define BF_SHF(x) (__builtin_ffsll(x) - 1)
                                    ^
../drivers/dma/hisilicon/hisi_dmadev.c:593:27: note: in expansion of macro ‘FIELD_GET’
    hw->status[csq_head] = FIELD_GET(CQE_STATUS_MASK,
                           ^~~~~~~~~
../drivers/dma/hisilicon/hisi_dmadev.h:160:26: note: in expansion of macro ‘GENMASK’
 #define CQE_STATUS_MASK  GENMASK(63, 49)
                          ^~~~~~~
../drivers/dma/hisilicon/hisi_dmadev.c:593:37: note: in expansion of macro ‘CQE_STATUS_MASK’
    hw->status[csq_head] = FIELD_GET(CQE_STATUS_MASK,
                                     ^~~~~~~~~~~~~~~
../drivers/dma/hisilicon/hisi_dmadev.h:17:36: error: right shift count is negative [-Werror=shift-count-negative]
   ((typeof(mask))(((reg) & (mask)) >> BF_SHF(mask)))
                                    ^
../drivers/dma/hisilicon/hisi_dmadev.c:593:27: note: in expansion of macro ‘FIELD_GET’
    hw->status[csq_head] = FIELD_GET(CQE_STATUS_MASK,
                           ^~~~~~~~~
cc1: all warnings being treated as errors
[738/2498] Generating rte_dma_hisilicon_mingw with a custom command.
[739/2498] Compiling C object 'lib/76b5a35@@rte_pipeline@sta/pipeline_rte_table_action.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-10-30 11:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211030103619.29924-7-fengchengwen@huawei.com>
2021-10-30 10:42 ` [dpdk-test-report] |SUCCESS| pw103265 " checkpatch
2021-10-30 11:39 ` 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=20211030113918.12198-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=fengchengwen@huawei.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).