automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, "Kusztal,
	ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Subject: |WARNING| pw127647 [PATCH] [v2] crypto/qat: add SM3 HMAC to gen4 dev
Date: Sun, 28 May 2023 12:47:55 -0700 (PDT)	[thread overview]
Message-ID: <6473afeb.c80a0220.dd97d.b3efSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/127647

_Testing issues_

Submitter: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
Date: Sunday, May 28 2023 17:36:25 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c9df59bcc9bec67783de98486879594e52bdc418

127647 --> testing fail

Test environment and result as below:

+--------------+----------------------+
| Environment  | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | WARN                 |
+--------------+----------------------+

==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
[655/3240] Compiling C object 'drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_dev_qat_crypto_pmd_gen4.c.o'.
FAILED: drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_dev_qat_crypto_pmd_gen4.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_dev_qat_crypto_pmd_gen4.c.o' -MF 'drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_dev_qat_crypto_pmd_gen4.c.o.d' -o 'drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_dev_qat_crypto_pmd_gen4.c.o' -c ../drivers/crypto/qat/dev/qat_crypto_pmd_gen4.c
In file included from ../drivers/crypto/qat/dev/qat_crypto_pmd_gen4.c:8:
../drivers/common/qat/../../crypto/qat/qat_sym.h:61:13: error: 'RTE_CRYPTO_AUTH_SM3_HMAC' undeclared here (not in a function); did you mean 'RTE_CRYPTO_AUTH_SHA1_HMAC'?
61 |     .algo = RTE_CRYPTO_AUTH_##n,  \
|             ^~~~~~~~~~~~~~~~
../drivers/crypto/qat/dev/qat_crypto_pmd_gen4.c:106:2: note: in expansion of macro 'QAT_SYM_AUTH_CAP'
106 |  QAT_SYM_AUTH_CAP(SM3_HMAC,
|  ^~~~~~~~~~~~~~~~
[656/3240] Compiling C object 'drivers/common/sfc_efx/base/932d09a@@sfc_base@sta/efx_bootcfg.c.o'.
[657/3240] Generating eal.sym_chk with a meson_exe.py custom command.
[658/3240] Generating vhost.sym_chk with a meson_exe.py custom command.
[659/3240] Generating rte_bus_dpaa.sym_chk with a meson_exe.py custom command.
[660/3240] Generating rte_bus_fslmc.sym_chk with a meson_exe.py custom command.
[661/3240] Compiling C object 'lib/76b5a35@@rte_pipeline@sta/pipeline_rte_table_action.c.o'.
[662/3240] Compiling C object 'drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_dev_qat_crypto_pmd_gen3.c.o'.
[663/3240] Compiling C object 'drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_dev_qat_sym_pmd_gen1.c.o'.
[664/3240] Compiling C object 'drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_qat_asym.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====

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/26427/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2023-05-28 19:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-28 19:47 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-28 19:27 dpdklab
2023-05-28 19:07 dpdklab
2023-05-28 19:06 dpdklab
2023-05-28 19:05 dpdklab
2023-05-28 19:05 dpdklab
2023-05-28 19:04 dpdklab
2023-05-28 19:04 dpdklab
2023-05-28 19:03 dpdklab
2023-05-28 19:03 dpdklab
2023-05-28 19:01 dpdklab
2023-05-28 19:00 dpdklab
2023-05-28 18:58 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=6473afeb.c80a0220.dd97d.b3efSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).