From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Sunyang Wu <sunyang.wu@jaguarmicro.com>,
dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
Sunyang Wu <sunyang.wu@jaguarmicro.com>
Subject: |FAILURE| pw124564 [PATCH] crypto/openssl: support SM3/SM4 in openssl
Date: Tue, 28 Feb 2023 12:01:16 +0000 (UTC) [thread overview]
Message-ID: <20230228120116.8039C601B1@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-testing
Test-Status: FAILURE
http://dpdk.org/patch/124564
_Testing issues_
Submitter: Sunyang Wu <sunyang.wu@jaguarmicro.com>
Date: Tuesday, February 28 2023 08:54:10
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7710b5d15a014872a3aaf646668dafa928ca8473
124564 --> testing fail
Test environment and result as below:
+---------------------+--------------------+----------------------+----------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_unit_test |
+=====================+====================+======================+================+
| FreeBSD 13 | FAIL | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+----------------+
| Windows Server 2019 | PASS | PASS | PASS |
+---------------------+--------------------+----------------------+----------------+
| CentOS Stream 8 | FAIL | SKIPPED | FAIL |
+---------------------+--------------------+----------------------+----------------+
| Debian Bullseye | FAIL | SKIPPED | FAIL |
+---------------------+--------------------+----------------------+----------------+
| Debian Buster | FAIL | SKIPPED | FAIL |
+---------------------+--------------------+----------------------+----------------+
| CentOS Stream 9 | FAIL | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+----------------+
| Ubuntu 22.04 | FAIL | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+----------------+
| openSUSE Leap 15 | FAIL | SKIPPED | FAIL |
+---------------------+--------------------+----------------------+----------------+
| RHEL 7 | SKIPPED | SKIPPED | FAIL |
+---------------------+--------------------+----------------------+----------------+
| RHEL8 | SKIPPED | SKIPPED | FAIL |
+---------------------+--------------------+----------------------+----------------+
==== 20 line log output for RHEL8 (dpdk_unit_test): ====
^
../drivers/crypto/openssl/rte_openssl_pmd.c:249:12: error: implicit declaration of function 'EVP_sm4_ctr'; did you mean 'NID_sm4_ctr'? [-Werror=implicit-function-declaration]
*algo = EVP_sm4_ctr();
^~~~~~~~~~~
NID_sm4_ctr
../drivers/crypto/openssl/rte_openssl_pmd.c:249:12: error: nested extern declaration of 'EVP_sm4_ctr' [-Werror=nested-externs]
../drivers/crypto/openssl/rte_openssl_pmd.c:249:10: error: assignment to 'const EVP_CIPHER *' {aka 'const struct evp_cipher_st *'} from 'int' makes pointer from integer without a cast [-Werror=int-conversion]
*algo = EVP_sm4_ctr();
^
../drivers/crypto/openssl/rte_openssl_pmd.c:229:4: error: this statement may fall through [-Werror=implicit-fallthrough=]
switch (keylen) {
^~~~~~
../drivers/crypto/openssl/rte_openssl_pmd.c:242:3: note: here
case RTE_CRYPTO_CIPHER_SM4_ECB:
^~~~
cc1: all warnings being treated as errors
[2207/3163] Compiling C object 'drivers/a715181@@tmp_rte_crypto_scheduler@sta/crypto_scheduler_rte_cryptodev_scheduler.c.o'.
[2208/3163] Compiling C object 'drivers/a715181@@tmp_rte_crypto_scheduler@sta/crypto_scheduler_scheduler_multicore.c.o'.
[2209/3163] Compiling C object 'drivers/a715181@@tmp_rte_crypto_octeontx@sta/crypto_octeontx_otx_cryptodev_ops.c.o'.
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)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 11.3.1-2
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
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)
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25556/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-28 12:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 12:01 dpdklab [this message]
[not found] <20230228085410.27972-1-sunyang.wu@jaguarmicro.com>
2023-02-28 10:19 ` 0-day Robot
2023-03-01 8:20 ` qemudev
-- strict thread matches above, loose matches on Subject: below --
2023-02-28 12:16 dpdklab
2023-02-28 12:15 dpdklab
2023-02-28 12:13 dpdklab
2023-02-28 12:12 dpdklab
2023-02-28 12:12 dpdklab
2023-02-28 12:11 dpdklab
2023-02-28 12:10 dpdklab
2023-02-28 12:01 dpdklab
2023-02-28 11:57 dpdklab
2023-02-28 11:56 dpdklab
2023-02-28 11:55 dpdklab
2023-02-28 11:53 dpdklab
2023-02-28 11:47 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=20230228120116.8039C601B1@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=sunyang.wu@jaguarmicro.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).