automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: david.marchand@redhat.com, robot@bytheb.org
Subject: |FAILURE| pw112877 [PATCH v2] vhost/crypto: fix build with GCC 12
Date: Thu, 16 Jun 2022 08:39:55 -0400	[thread overview]
Message-ID: <20220616123955.28076-1-robot@bytheb.org> (raw)
In-Reply-To: <20220616093211.881984-1-david.marchand@redhat.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=pw|patchwork.dpdk.org|build|23566|SHA|8f470173c17e16bd8bfcf2ddae8c3e9491a072b5|passed|https://github.com/ovsrobot/dpdk/actions/runs/2508147123|[PATCH v2] test/ipsec: fix build with GCC 12|ovsrobot/dpdk|build, Size: 4260 bytes --]

From: robot@bytheb.org

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

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

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-static-i386" at step Build and test
####################################################################################
[799/3105] Compiling C object 'drivers/a715181@@rte_dma_ioat@sha/meson-generated_.._rte_dma_ioat.pmd.c.o'.
[800/3105] Linking target drivers/librte_dma_ioat.so.22.2.
[801/3105] Generating rte_dma_skeleton_def with a custom command.
[802/3105] Generating rte_dma_skeleton_mingw with a custom command.
[803/3105] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_vhost_crypto.c.o'.
FAILED: lib/76b5a35@@rte_vhost@sta/vhost_vhost_crypto.c.o 
ccache gcc -Ilib/76b5a35@@rte_vhost@sta -Ilib -I../lib -Ilib/vhost -I../lib/vhost -I. -I../ -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/telemetry/../metrics -I../lib/telemetry/../metrics -Ilib/telemetry -I../lib/telemetry -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/cryptodev -I../lib/cryptodev -Ilib/rcu -I../lib/rcu -Ilib/hash -I../lib/hash -Ilib/pci -I../lib/pci -Ilib/dmadev -I../lib/dmadev -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -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 -Wno-pointer-to-int-cast -D_GNU_SOURCE -m32 -fPIC -march=corei7 -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DVHOST_GCC_UNROLL_PRAGMA -fno-strict-aliasing -DRTE_LOG_DEFAULT_LOGTYPE=lib.vhost  -MD -MQ 'lib/76b5a35@@rte_vhost@sta/vhost_vhost_crypto.c.o' -MF 'lib/76b5a35@@rte_vhost@sta/vhost_vhost_crypto.c.o.d' -o 'lib/76b5a35@@rte_vhost@sta/vhost_vhost_crypto.c.o' -c ../lib/vhost/vhost_crypto.c
In file included from ../lib/eal/include/rte_log.h:25,
                 from ../lib/eal/include/rte_debug.h:17,
                 from ../lib/eal/include/rte_bitops.h:17,
                 from ../lib/eal/include/rte_memory.h:22,
                 from ../lib/eal/include/rte_malloc.h:17,
                 from ../lib/vhost/vhost_crypto.c:4:
../lib/vhost/vhost_crypto.c: In function ‘copy_data_from_desc’:
../lib/eal/include/rte_common.h:293:30: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]
  293 | #define RTE_PTR_ADD(ptr, x) ((void*)((uintptr_t)(ptr) + (x)))
      |                              ^
../lib/vhost/vhost_crypto.c:588:9: note: in expansion of macro ‘RTE_PTR_ADD’
  588 |   dst = RTE_PTR_ADD(dst, len);
      |         ^~~~~~~~~~~
cc1: all warnings being treated as errors
[804/3105] Compiling C object 'drivers/a715181@@tmp_rte_net_af_packet@sta/net_af_packet_rte_eth_af_packet.c.o'.
[805/3105] Compiling C object 'drivers/a715181@@tmp_rte_dma_skeleton@sta/dma_skeleton_skeleton_dmadev.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-static-i386" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2022-06-16 12:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220616093211.881984-1-david.marchand@redhat.com>
2022-06-16  9:33 ` |SUCCESS| " checkpatch
2022-06-16 12:39 ` 0-day Robot [this message]
2022-06-16 14:53 |FAILURE| pw112877 [PATCH] [v2] " dpdklab

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=20220616123955.28076-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=david.marchand@redhat.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).