From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: |FAILURE| pw117067-117068 [PATCH] [2/2] crypto/qat: fix not set rsa lengths
Date: Wed, 28 Sep 2022 18:14:06 +0000 (UTC) [thread overview]
Message-ID: <20220928181406.40B4E601BB@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 6988 bytes --]
Test-Label: iol-x86_64-compile-testing
Test-Status: FAILURE
http://dpdk.org/patch/117068
_Testing issues_
Submitter: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Date: Wednesday, September 28 2022 15:58:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3fe71706abc1f13294c82477a0538047f8e4ebbf
117067-117068 --> testing fail
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Arch Linux | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 18.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 31 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL 7 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 34 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 32 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 33 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 34 clang | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
==== 20 line log output for Arch Linux (dpdk_meson_compile): ====
[819/3386] Compiling C object 'drivers/a715181@@tmp_rte_common_qat@sta/compress_qat_qat_comp_pmd.c.o'.
[820/3386] Compiling C object 'drivers/a715181@@tmp_rte_common_qat@sta/compress_qat_qat_comp.c.o'.
[821/3386] Compiling C object 'drivers/a715181@@tmp_rte_common_qat@sta/compress_qat_dev_qat_comp_pmd_gen1.c.o'.
[822/3386] Compiling C object 'drivers/a715181@@tmp_rte_common_qat@sta/compress_qat_dev_qat_comp_pmd_gen2.c.o'.
[823/3386] Compiling C object 'drivers/a715181@@tmp_rte_common_qat@sta/compress_qat_dev_qat_comp_pmd_gen3.c.o'.
[824/3386] Compiling C object 'drivers/a715181@@tmp_rte_common_qat@sta/compress_qat_dev_qat_comp_pmd_gen4.c.o'.
[825/3386] Compiling C object 'drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_qat_asym.c.o'.
FAILED: drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_qat_asym.c.o
cc -Idrivers/a715181@@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/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/pci -I../lib/pci -Ilib/cryptodev -I../lib/cryptodev -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/rcu -I../lib/rcu -Ilib/net -I../lib/net -Ilib/compressdev -I../lib/compressdev -Ilib/security -I../lib/security -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -O3 -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-zero-length-bounds -D_GNU_SOURCE -fPIC -march=native -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DBUILD_QAT_SYM -DBUILD_QAT_ASYM -DRTE_LOG_DEFAULT_LOGTYPE=pmd.common.qat -MD -MQ 'drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_qat_asym.c.o' -MF 'drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_qat_asym.c.o.d' -o 'drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_qat_asym.c.o' -c ../drivers/crypto/qat/qat_asym.c
In function ‘cleanup’,
inlined from ‘qat_asym_process_response’ at ../drivers/crypto/qat/qat_asym.c:927:2:
../drivers/crypto/qat/qat_asym.c:134:18: error: ‘xform’ may be used uninitialized [-Werror=maybe-uninitialized]
134 | if (xform->xform_type == RTE_CRYPTO_ASYM_XFORM_MODEX)
| ~~~~~^~~~~~~~~~~~
../drivers/crypto/qat/qat_asym.c: In function ‘qat_asym_process_response’:
../drivers/crypto/qat/qat_asym.c:881:39: note: ‘xform’ was declared here
881 | struct rte_crypto_asym_xform *xform;
| ^~~~~
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
Fedora 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)
Fedora 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
Fedora 33
Kernel: 5.4.0-72-generic
Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Fedora 34 clang
Kernel: 5.4.0-72-generic
Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/23683/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-09-28 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 18:14 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-28 18:50 dpdklab
2022-09-28 18:08 dpdklab
2022-09-28 18:04 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=20220928181406.40B4E601BB@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=arkadiuszx.kusztal@intel.com \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).