automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Jack Bond-Preston <jack.bond-preston@foss.arm.com>, zhoumin@loongson.cn
Subject: |FAILURE| pw140623-140627 [PATCH 5/5] crypto/openssl: only set cipher padding once
Date: Tue, 4 Jun 2024 09:18:22 +0800	[thread overview]
Message-ID: <202406040118.4541IMWi2445616@localhost.localdomain> (raw)
In-Reply-To: <20240603160119.1279476-6-jack.bond-preston@foss.arm.com>

Test-Label: loongarch-compilation
Test-Status: FAILURE
http://dpdk.org/patch/140627

_ninja build failure_

Submitter: Jack Bond-Preston <jack.bond-preston@foss.arm.com>
Date: Mon,  3 Jun 2024 16:01:15 +0000
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: 367b8db312517edb9f5340d280e77b1437d84dd3

140623-140627 --> ninja build failed

Test environment and result as below:

+---------------------+----------------+
|     Environment     | compilation    |
+---------------------+----------------+
| Loongnix-Server 8.3 | FAIL           |
+---------------------+----------------+

Loongnix-Server 8.3
    Kernel: 4.19.190+
    Compiler: gcc 8.3


Ninja build logs:
-------------------------------BEGIN LOGS----------------------------
FAILED: drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd_ops.c.o
cc -Idrivers/libtmp_rte_crypto_openssl.a.p -Idrivers -I../drivers -Idrivers/crypto/openssl -I../drivers/crypto/openssl -Ilib/cryptodev -I../lib/cryptodev -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/loongarch/include -I../lib/eal/loongarch/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/rcu -I../lib/rcu -Idrivers/bus/vdev -I../drivers/bus/vdev -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c11 -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-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=loongarch64 -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DRTE_LOG_DEFAULT_LOGTYPE=pmd.crypto.openssl -MD -MQ drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd_ops.c.o -MF drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd_ops.c.o.d -o drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd_ops.c.o -c ../drivers/crypto/openssl/rte_openssl_pmd_ops.c
In file included from ../drivers/crypto/openssl/rte_openssl_pmd_ops.c:11:
./drivers/crypto/openssl/openssl_pmd_private.h:91:12: error: field ‘hmac’ has incomplete type
HMAC_CTX hmac;
^~~~
./drivers/crypto/openssl/openssl_pmd_private.h:92:12: error: field ‘cmac’ has incomplete type
CMAC_CTX cmac;
^~~~
[1846/2497] Compiling C object drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o
FAILED: drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o
cc -Idrivers/libtmp_rte_crypto_openssl.a.p -Idrivers -I../drivers -Idrivers/crypto/openssl -I../drivers/crypto/openssl -Ilib/cryptodev -I../lib/cryptodev -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/loongarch/include -I../lib/eal/loongarch/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/rcu -I../lib/rcu -Idrivers/bus/vdev -I../drivers/bus/vdev -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c11 -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-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=loongarch64 -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DRTE_LOG_DEFAULT_LOGTYPE=pmd.crypto.openssl -MD -MQ drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o -MF drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o.d -o drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o -c ../drivers/crypto/openssl/rte_openssl_pmd.c
In file included from ../drivers/crypto/openssl/rte_openssl_pmd.c:18:
./drivers/crypto/openssl/openssl_pmd_private.h:91:12: error: field ‘hmac’ has incomplete type
HMAC_CTX hmac;
^~~~
./drivers/crypto/openssl/openssl_pmd_private.h:92:12: error: field ‘cmac’ has incomplete type
CMAC_CTX cmac;
^~~~
[1847/2497] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn10k_tls.c.o
[1848/2497] Compiling C object drivers/libtmp_rte_crypto_octeontx.a.p/crypto_octeontx_otx_cryptodev_hw_access.c.o
[1849/2497] Generating rte_crypto_null.pmd.c with a custom command
[1850/2497] Compiling C object drivers/libtmp_rte_crypto_virtio.a.p/crypto_virtio_virtio_pci.c.o
[1851/2497] Compiling C object drivers/libtmp_rte_compress_octeontx.a.p/compress_octeontx_otx_zip.c.o
[1852/2497] Compiling C object drivers/libtmp_rte_crypto_nitrox.a.p/crypto_nitrox_nitrox_sym.c.o
[1853/2497] Compiling C object drivers/libtmp_rte_crypto_scheduler.a.p/crypto_scheduler_rte_cryptodev_scheduler.c.o
[1854/2497] Generating rte_crypto_bcmfs.pmd.c with a custom command
[1855/2497] Compiling C object drivers/libtmp_rte_crypto_virtio.a.p/crypto_virtio_virtqueue.c.o
[1856/2497] Compiling C object drivers/libtmp_rte_crypto_virtio.a.p/crypto_virtio_virtio_rxtx.c.o
[1857/2497] Compiling C object drivers/libtmp_rte_compress_nitrox.a.p/compress_nitrox_nitrox_comp_reqmgr.c.o
[1858/2497] Compiling C object drivers/libtmp_rte_raw_ntb.a.p/raw_ntb_ntb.c.o
[1859/2497] Compiling C object drivers/libtmp_rte_compress_nitrox.a.p/compress_nitrox_nitrox_comp.c.o
[1860/2497] Compiling C object drivers/libtmp_rte_crypto_virtio.a.p/crypto_virtio_virtio_cryptodev.c.o
[1861/2497] Generating rte_net_vmxnet3.pmd.c with a custom command
[1862/2497] Compiling C object drivers/libtmp_rte_crypto_dpaa2_sec.a.p/crypto_dpaa2_sec_dpaa2_sec_raw_dp.c.o
[1863/2497] Generating rte_net_vhost.sym_chk with a custom command (wrapped by meson to capture output)
[1864/2497] Compiling C object drivers/libtmp_rte_crypto_dpaa_sec.a.p/crypto_dpaa_sec_dpaa_sec_raw_dp.c.o
[1865/2497] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cnxk_cryptodev_ops.c.o
[1866/2497] Generating rte_net_ixgbe.sym_chk with a custom command (wrapped by meson to capture output)
[1867/2497] Generating rte_net_qede.pmd.c with a custom command
[1868/2497] Compiling C object drivers/libtmp_rte_net_virtio.a.p/net_virtio_virtio_rxtx.c.o
[1869/2497] Compiling C object drivers/libtmp_rte_compress_octeontx.a.p/compress_octeontx_otx_zip_pmd.c.o
[1870/2497] Compiling C object drivers/libtmp_rte_net_txgbe.a.p/net_txgbe_txgbe_rxtx.c.o
[1871/2497] Compiling C object drivers/libtmp_rte_crypto_ccp.a.p/crypto_ccp_ccp_crypto.c.o
[1872/2497] Compiling C object drivers/libtmp_rte_crypto_caam_jr.a.p/crypto_caam_jr_caam_jr.c.o
[1873/2497] Compiling C object drivers/libtmp_rte_crypto_dpaa_sec.a.p/crypto_dpaa_sec_dpaa_sec.c.o
[1874/2497] Compiling C object drivers/libtmp_rte_crypto_dpaa2_sec.a.p/crypto_dpaa2_sec_dpaa2_sec_dpseci.c.o
[1875/2497] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[1876/2497] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn9k_cryptodev_ops.c.o
[1877/2497] Compiling C object drivers/libtmp_rte_crypto_octeontx.a.p/crypto_octeontx_otx_cryptodev_ops.c.o
[1878/2497] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn10k_cryptodev_ops.c.o
ninja: build stopped: subcommand failed.
-------------------------------END LOGS------------------------------


      parent reply	other threads:[~2024-06-04  1:47 UTC|newest]

Thread overview: 99+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240603160119.1279476-6-jack.bond-preston@foss.arm.com>
2024-06-03 16:03 ` |SUCCESS| pw140627 " checkpatch
2024-06-03 16:57 ` |SUCCESS| pw140623-140627 [PATCH] [5/5] crypto/openssl: only set cip dpdklab
2024-06-03 16:57 ` dpdklab
2024-06-03 16:57 ` dpdklab
2024-06-03 16:58 ` dpdklab
2024-06-03 16:59 ` |FAILURE| " dpdklab
2024-06-03 17:00 ` |SUCCESS| " dpdklab
2024-06-03 17:01 ` dpdklab
2024-06-03 17:01 ` |WARNING| " dpdklab
2024-06-03 17:02 ` dpdklab
2024-06-03 17:02 ` |SUCCESS| " dpdklab
2024-06-03 17:02 ` |WARNING| " dpdklab
2024-06-03 17:02 ` |FAILURE| " dpdklab
2024-06-03 17:03 ` dpdklab
2024-06-03 17:03 ` |SUCCESS| " dpdklab
2024-06-03 17:03 ` |WARNING| " dpdklab
2024-06-03 17:04 ` dpdklab
2024-06-03 17:04 ` dpdklab
2024-06-03 17:04 ` |SUCCESS| pw140627 [PATCH 5/5] crypto/openssl: only set cipher padding once 0-day Robot
2024-06-03 17:04 ` |WARNING| pw140623-140627 [PATCH] [5/5] crypto/openssl: only set cip dpdklab
2024-06-03 17:05 ` |SUCCESS| " dpdklab
2024-06-03 17:05 ` |WARNING| " dpdklab
2024-06-03 17:05 ` |FAILURE| " dpdklab
2024-06-03 17:05 ` dpdklab
2024-06-03 17:06 ` dpdklab
2024-06-03 17:06 ` dpdklab
2024-06-03 17:07 ` |SUCCESS| " dpdklab
2024-06-03 17:07 ` |FAILURE| " dpdklab
2024-06-03 17:07 ` |SUCCESS| " dpdklab
2024-06-03 17:07 ` dpdklab
2024-06-03 17:08 ` |FAILURE| " dpdklab
2024-06-03 17:09 ` |WARNING| " dpdklab
2024-06-03 17:09 ` |FAILURE| " dpdklab
2024-06-03 17:10 ` dpdklab
2024-06-03 17:10 ` |WARNING| " dpdklab
2024-06-03 17:10 ` |FAILURE| " dpdklab
2024-06-03 17:11 ` dpdklab
2024-06-03 17:11 ` |SUCCESS| " dpdklab
2024-06-03 17:12 ` |WARNING| " dpdklab
2024-06-03 17:12 ` |FAILURE| " dpdklab
2024-06-03 17:12 ` dpdklab
2024-06-03 17:12 ` dpdklab
2024-06-03 17:13 ` |SUCCESS| " dpdklab
2024-06-03 17:13 ` dpdklab
2024-06-03 17:13 ` dpdklab
2024-06-03 17:13 ` |FAILURE| " dpdklab
2024-06-03 17:13 ` dpdklab
2024-06-03 17:14 ` dpdklab
2024-06-03 17:14 ` dpdklab
2024-06-03 17:15 ` |WARNING| " dpdklab
2024-06-03 17:15 ` |FAILURE| " dpdklab
2024-06-03 17:15 ` dpdklab
2024-06-03 17:16 ` dpdklab
2024-06-03 17:16 ` dpdklab
2024-06-03 17:16 ` dpdklab
2024-06-03 17:16 ` |SUCCESS| " dpdklab
2024-06-03 17:17 ` |WARNING| " dpdklab
2024-06-03 17:17 ` |SUCCESS| " dpdklab
2024-06-03 17:17 ` |FAILURE| " dpdklab
2024-06-03 17:18 ` dpdklab
2024-06-03 17:18 ` dpdklab
2024-06-03 17:18 ` dpdklab
2024-06-03 17:19 ` dpdklab
2024-06-03 17:20 ` dpdklab
2024-06-03 17:20 ` |WARNING| " dpdklab
2024-06-03 17:20 ` |FAILURE| " dpdklab
2024-06-03 17:20 ` dpdklab
2024-06-03 17:23 ` dpdklab
2024-06-03 17:24 ` dpdklab
2024-06-03 17:24 ` dpdklab
2024-06-03 17:25 ` dpdklab
2024-06-03 17:26 ` dpdklab
2024-06-03 17:27 ` dpdklab
2024-06-03 17:27 ` dpdklab
2024-06-03 17:27 ` dpdklab
2024-06-03 17:28 ` dpdklab
2024-06-03 17:28 ` dpdklab
2024-06-03 17:29 ` dpdklab
2024-06-03 17:30 ` dpdklab
2024-06-03 17:32 ` dpdklab
2024-06-03 17:34 ` dpdklab
2024-06-03 17:34 ` |SUCCESS| " dpdklab
2024-06-03 17:34 ` |FAILURE| " dpdklab
2024-06-03 17:37 ` dpdklab
2024-06-03 17:37 ` dpdklab
2024-06-03 17:39 ` dpdklab
2024-06-03 17:40 ` dpdklab
2024-06-03 17:40 ` dpdklab
2024-06-03 17:42 ` dpdklab
2024-06-03 17:43 ` dpdklab
2024-06-03 17:47 ` dpdklab
2024-06-03 17:51 ` dpdklab
2024-06-03 17:51 ` dpdklab
2024-06-03 20:00 ` dpdklab
2024-06-03 20:02 ` dpdklab
2024-06-03 21:12 ` |SUCCESS| " dpdklab
2024-06-03 21:19 ` dpdklab
2024-06-03 21:44 ` |WARNING| " dpdklab
2024-06-04  1:18 ` qemudev [this message]

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=202406040118.4541IMWi2445616@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=jack.bond-preston@foss.arm.com \
    --cc=test-report@dpdk.org \
    --cc=zhoumin@loongson.cn \
    /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).