From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: adamx.dybkowski@intel.com, robot@bytheb.org
Subject: [dpdk-test-report] |FAILURE| pw88517 [dpdk-dev] [PATCH] crypto/qat: support Single-Pass GMAC on QAT GEN3
Date: Fri, 5 Mar 2021 08:57:17 -0500 [thread overview]
Message-ID: <20210305135717.32569-1-robot@bytheb.org> (raw)
In-Reply-To: <20210305124512.16286-1-adamx.dybkowski@intel.com>
From: robot@bytheb.org
Test-Label: github-robot
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/88517/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/624472569
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"
####################################################################################
[692/2571] Compiling C object 'drivers/drivers@@tmp_rte_mempool_bucket@sta/mempool_bucket_rte_mempool_bucket.c.o'.
[693/2571] Linking static target drivers/libtmp_rte_mempool_bucket.a.
[694/2571] Generating rte_bus_vmbus.sym_chk with a meson_exe.py custom command.
[695/2571] Linking target drivers/librte_bus_vmbus.so.21.2.
[696/2571] Generating rte_mempool_bucket.pmd.c with a custom command.
[697/2571] Compiling C object 'drivers/drivers@@rte_mempool_bucket@sta/meson-generated_.._rte_mempool_bucket.pmd.c.o'.
[698/2571] Linking static target drivers/librte_mempool_bucket.a.
[699/2571] Generating rte_mempool_bucket_def with a custom command.
[700/2571] Generating rte_mempool_bucket_mingw with a custom command.
[701/2571] Generating symbol file 'drivers/drivers@@rte_bus_vmbus@sha/librte_bus_vmbus.so.21.2.symbols'.
[702/2571] Compiling C object 'drivers/drivers@@rte_mempool_bucket@sha/meson-generated_.._rte_mempool_bucket.pmd.c.o'.
[703/2571] Compiling C object 'drivers/drivers@@tmp_rte_mempool_dpaa@sta/mempool_dpaa_dpaa_mempool.c.o'.
[704/2571] Compiling C object 'drivers/drivers@@tmp_rte_common_qat@sta/common_qat_qat_qp.c.o'.
FAILED: drivers/drivers@@tmp_rte_common_qat@sta/common_qat_qat_qp.c.o
ccache gcc -Idrivers/drivers@@tmp_rte_common_qat@sta -Idrivers -I../drivers -Idrivers/common/qat -I../drivers/common/qat -I../drivers/common/qat/qat_adf -I../drivers/common/qat/../../crypto/qat -I../drivers/common/qat/../../compress/qat -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -I. -I../ -Iconfig -I../config -Ilib/librte_eal/include -I../lib/librte_eal/include -Ilib/librte_eal/linux/include -I../lib/librte_eal/linux/include -Ilib/librte_eal/x86/include -I../lib/librte_eal/x86/include -Ilib/librte_eal/common -I../lib/librte_eal/common -Ilib/librte_eal -I../lib/librte_eal -Ilib/librte_kvargs -I../lib/librte_kvargs -Ilib/librte_telemetry/../librte_metrics -I../lib/librte_telemetry/../librte_metrics -Ilib/librte_telemetry -I../lib/librte_telemetry -Ilib/librte_pci -I../lib/librte_pci -Ilib/librte_cryptodev -I../lib/librte_cryptodev -Ilib/librte_mbuf -I../lib/librte_mbuf -Ilib/librte_mempool -I../lib/librte_mempool -Ilib/librte_ring -I../lib/librte_ring -Ilib/librte_rcu -I../lib/librte_rcu -Ilib/librte_net -I../lib/librte_net -Ilib/librte_compressdev -I../lib/librte_compressdev -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Werror -O2 -g -include rte_config.h -Wextra -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-missing-field-initializers -Wno-pointer-to-int-cast -D_GNU_SOURCE -m32 -fPIC -march=corei7 -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -MD -MQ 'drivers/drivers@@tmp_rte_common_qat@sta/common_qat_qat_qp.c.o' -MF 'drivers/drivers@@tmp_rte_common_qat@sta/common_qat_qat_qp.c.o.d' -o 'drivers/drivers@@tmp_rte_common_qat@sta/common_qat_qat_qp.c.o' -c ../drivers/common/qat/qat_qp.c
In file included from ../drivers/common/qat/qat_qp.c:18:0:
../drivers/common/qat/../../crypto/qat/qat_sym.h: In function ‘qat_sym_process_response’:
../drivers/common/qat/../../crypto/qat/qat_sym.h:307:8: error: unused parameter ‘op_cookie’ [-Werror=unused-parameter]
void *op_cookie)
^~~~~~~~~
cc1: all warnings being treated as errors
[705/2571] Linking static target drivers/libtmp_rte_mempool_dpaa.a.
[706/2571] Generating rte_mempool_bucket.sym_chk with a meson_exe.py custom command.
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-03-05 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210305124512.16286-1-adamx.dybkowski@intel.com>
2021-03-05 12:47 ` [dpdk-test-report] |WARNING| pw88517 " checkpatch
2021-03-05 13:55 ` [dpdk-test-report] |FAILURE| pw88517 " 0-day Robot
2021-03-05 13:57 ` 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=20210305135717.32569-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=adamx.dybkowski@intel.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).