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: |FAILURE| pw127647 [PATCH] [v2] crypto/qat: add SM3 HMAC to gen4 dev
Date: Sun, 28 May 2023 13:05:22 -0700 (PDT) [thread overview]
Message-ID: <6473b402.b00a0220.84297.9c84SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-x86_64-compile-testing
Test-Status: FAILURE
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_meson_compile |
+==================+====================+
| FreeBSD 13 | FAIL |
+------------------+--------------------+
| CentOS Stream 8 | FAIL |
+------------------+--------------------+
| CentOS Stream 9 | FAIL |
+------------------+--------------------+
| Fedora 37 | FAIL |
+------------------+--------------------+
| Debian Bullseye | FAIL |
+------------------+--------------------+
| Fedora 38 | FAIL |
+------------------+--------------------+
| openSUSE Leap 15 | FAIL |
+------------------+--------------------+
| Debian Buster | FAIL |
+------------------+--------------------+
| RHEL 7 | FAIL |
+------------------+--------------------+
| Ubuntu 22.04 | FAIL |
+------------------+--------------------+
| Ubuntu 20.04 | FAIL |
+------------------+--------------------+
| RHEL8 | FAIL |
+------------------+--------------------+
| Alpine | FAIL |
+------------------+--------------------+
==== 20 line log output for Alpine (dpdk_meson_compile): ====
[2165/3100] Compiling C object 'drivers/common/sfc_efx/base/932d09a@@sfc_base@sta/efx_mac.c.o'.
[2166/3100] Compiling C object 'drivers/common/sfc_efx/base/932d09a@@sfc_base@sta/efx_lic.c.o'.
[2167/3100] Compiling C object 'drivers/common/sfc_efx/base/932d09a@@sfc_base@sta/efx_intr.c.o'.
[2168/3100] Compiling C object 'drivers/common/sfc_efx/base/932d09a@@sfc_base@sta/efx_hash.c.o'.
[2169/3100] Compiling C object 'drivers/common/sfc_efx/base/932d09a@@sfc_base@sta/efx_filter.c.o'.
[2170/3100] Compiling C object 'drivers/common/sfc_efx/base/932d09a@@sfc_base@sta/efx_evb.c.o'.
[2171/3100] Compiling C object 'drivers/common/sfc_efx/base/932d09a@@sfc_base@sta/efx_ev.c.o'.
[2172/3100] Compiling C object 'drivers/common/sfc_efx/base/932d09a@@sfc_base@sta/efx_crc32.c.o'.
[2173/3100] Compiling C object 'drivers/common/sfc_efx/base/932d09a@@sfc_base@sta/efx_bootcfg.c.o'.
[2174/3100] Linking static target drivers/librte_common_sfc_efx.a.
[2175/3100] Generating rte_common_sfc_efx.sym_chk with a meson_exe.py custom command.
[2176/3100] Linking static target drivers/common/sfc_efx/base/libsfc_base.a.
[2177/3100] Compiling C object 'drivers/a715181@@tmp_rte_common_qat@sta/crypto_qat_dev_qat_crypto_pmd_gen4.c.o'.
In file included from ^[[01m^[[K../drivers/crypto/qat/dev/qat_crypto_pmd_gen4.c:8^[[m^[[K:
^[[01m^[[K../drivers/common/qat/../../crypto/qat/qat_sym.h:61:41:^[[m^[[K ^[[01;31m^[[Kerror: ^[[m^[[K'^[[01m^[[KRTE_CRYPTO_AUTH_SM3_HMAC^[[m^[[K' undeclared here (not in a function); did you mean '^[[01m^[[KRTE_CRYPTO_AUTH_SHA1_HMAC^[[m^[[K'?
61 | .algo = ^[[01;31m^[[KRTE_CRYPTO_AUTH_^[[m^[[K##n, \
| ^[[01;31m^[[K^~~~~~~~~~~~~~~~^[[m^[[K
^[[01m^[[K../drivers/crypto/qat/dev/qat_crypto_pmd_gen4.c:106:9:^[[m^[[K ^[[01;36m^[[Knote: ^[[m^[[Kin expansion of macro '^[[01m^[[KQAT_SYM_AUTH_CAP^[[m^[[K'
106 | ^[[01;36m^[[KQAT_SYM_AUTH_CAP^[[m^[[K(SM3_HMAC,
| ^[[01;36m^[[K^~~~~~~~~~~~~~~~^[[m^[[K
==== End log output ====
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
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)
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
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)
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
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/
next reply other threads:[~2023-05-28 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 20:05 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-28 20:47 dpdklab
2023-05-28 19:48 dpdklab
2023-05-28 19:22 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=6473b402.b00a0220.84297.9c84SMTPIN_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).