From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: |FAILURE| pw126265-126266 [PATCH] [2/2] crypto/qat: add sm3 hmac
Date: Wed, 19 Apr 2023 20:42:42 +0000 (UTC) [thread overview]
Message-ID: <20230419204242.B683960092@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-x86_64-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/126266
_Testing issues_
Submitter: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Date: Wednesday, April 19 2023 19:51:09
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd
126265-126266 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | FAIL |
+---------------------+----------------+
==== 20 line log output for Ubuntu 20.04 (dpdk_unit_test): ====
[777/3213] Compiling C object 'drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_qat_sym_session.c.o'.
FAILED: drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_qat_sym_session.c.o
ccache 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 -Werro
r -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 -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_sym_session.c.o' -MF 'drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_qat_sym_session.c.o.d' -o 'drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_qat_sym_session.c.o' -c ../drivers/crypto/qat/qat_sym_session.c
../drivers/crypto/qat/qat_sym_session.c: In function 'qat_sym_session_configure_auth':
../drivers/crypto/qat/qat_sym_session.c:698:7: error: 'RTE_CRYPTO_AUTH_SM3_HMAC' undeclared (first use in this function); did you mean 'RTE_CRYPTO_AUTH_SHA1_HMAC'?
698 | case RTE_CRYPTO_AUTH_SM3_HMAC:
| ^~~~~~~~~~~~~~~~~~~~~~~~
| RTE_CRYPTO_AUTH_SHA1_HMAC
../drivers/crypto/qat/qat_sym_session.c:698:7: note: each undeclared identifier is reported only once for each function it appears in
../drivers/crypto/qat/qat_sym_session.c:700:22: error: this statement may fall through [-Werror=implicit-fallthrough=]
700 | session->auth_mode = ICP_QAT_HW_AUTH_MODE2;
| ~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~
../drivers/crypto/qat/qat_sym_session.c:701:2: note: here
701 | case RTE_CRYPTO_AUTH_SM3:
| ^~~~
cc1: all warnings being treated as errors
[778/3213] Generating rte_common_mlx5.sym_chk with a meson_exe.py custom command.
[779/3213] Compiling C object 'drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_dev_qat_sym_pmd_gen1.c.o'.
[780/3213] Generating rte_common_cnxk.sym_chk with a meson_exe.py custom command.
ninja: build stopped: subcommand failed.
==== End log output ====
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26051/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-19 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 20:42 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-19 21:02 dpdklab
2023-04-19 20:47 dpdklab
2023-04-19 20:39 dpdklab
[not found] <20230419195109.1659341-2-arkadiuszx.kusztal@intel.com>
2023-04-19 19:40 ` |FAILURE| pw126265-126266 [PATCH 2/2] " qemudev
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=20230419204242.B683960092@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=arkadiuszx.kusztal@intel.com \
--cc=david.marchand@redhat.com \
--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).