From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Stephen Hemminger <stephen@networkplumber.org>
Subject: |FAILURE| pw134435-134444 [PATCH] [v2,10/10] common/dpaxx: replace z
Date: Thu, 16 Nov 2023 21:34:29 -0800 (PST) [thread overview]
Message-ID: <6556fb65.050a0220.163f4.1d1fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/134444
_Testing issues_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, November 17 2023 04:03:22
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6d7129a6e93b7cb52efff009b29ef1a0f2cb76b4
134435-134444 --> testing fail
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang) | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
==== 20 line log output for Fedora 38 (ARM Clang) (dpdk_meson_compile): ====
[2187/3112] Compiling C object 'drivers/a715181@@tmp_rte_crypto_bcmfs@sta/crypto_bcmfs_bcmfs_sym_capabilities.c.o'.
[2188/3112] Compiling C object 'drivers/a715181@@tmp_rte_crypto_bcmfs@sta/crypto_bcmfs_bcmfs_sym_session.c.o'.
[2189/3112] Compiling C object 'drivers/a715181@@tmp_rte_crypto_bcmfs@sta/crypto_bcmfs_bcmfs_sym.c.o'.
[2190/3112] Compiling C object 'drivers/a715181@@tmp_rte_crypto_bcmfs@sta/crypto_bcmfs_bcmfs_sym_engine.c.o'.
[2191/3112] Linking static target drivers/libtmp_rte_crypto_bcmfs.a.
[2192/3112] Generating rte_crypto_bcmfs.pmd.c with a custom command.
[2193/3112] Compiling C object 'drivers/a715181@@rte_crypto_bcmfs@sta/meson-generated_.._rte_crypto_bcmfs.pmd.c.o'.
[2194/3112] Linking static target drivers/librte_crypto_bcmfs.a.
[2195/3112] Compiling C object 'drivers/a715181@@rte_crypto_bcmfs@sha/meson-generated_.._rte_crypto_bcmfs.pmd.c.o'.
[2196/3112] Linking target drivers/librte_crypto_bcmfs.so.24.0.
[2197/3112] Compiling C object 'drivers/a715181@@tmp_rte_crypto_caam_jr@sta/crypto_caam_jr_caam_jr_capabilities.c.o'.
[2198/3112] Compiling C object 'drivers/a715181@@tmp_rte_crypto_caam_jr@sta/crypto_caam_jr_caam_jr_hw.c.o'.
FAILED: drivers/a715181@@tmp_rte_crypto_caam_jr@sta/crypto_caam_jr_caam_jr_hw.c.o
clang -Idrivers/a715181@@tmp_rte_crypto_caam_jr@sta -Idrivers -I../drivers -Idrivers/crypto/caam_jr -I../drivers/crypto/caam_jr -I../drivers/crypto/caam_jr/../../bus/dpaa/include/ -Idrivers/crypto/caam_jr/../../common/dpaax/ -I../drivers/crypto/caam_jr/../../common/dpaax/ -I../drivers/crypto/caam_jr/../../common/dpaax/caamflib/ -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/arm/include -I../lib/eal/arm/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/telemetry/../metrics -I../lib/telemetry/../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 -Idrivers/bus/dpaa -I../drivers/bus/dpaa -I../drivers/bus/dpaa/include -I../drivers/bus/dpaa/base/qbman -Idrivers/co
mmon/dpaax -I../drivers/common/dpaax -I../drivers/common/dpaax/caamflib -Ilib/eventdev -I../lib/eventdev -Ilib/ethdev -I../lib/ethdev -Ilib/net -I../lib/net -Ilib/meter -I../lib/meter -Ilib/hash -I../lib/hash -Ilib/timer -I../lib/timer -Ilib/dmadev -I../lib/dmadev -Ilib/security -I../lib/security -Xclang -fcolor-diagnostics -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -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-address-of-packed-member -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=armv8.1-a+crc+crypto -mcpu=thunderx2t99 -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -DRTE_LOG_DEFAULT_LOGTYPE=pmd.crypto.caam_jr -DRTE_ANNOTATE_LOCKS -Wthread-safety -MD -MQ 'drivers/a715181@@tmp_rte_crypto_caam_jr@sta/crypto_caam_jr_caam_jr_hw.c.o'
-MF 'drivers/a715181@@tmp_rte_crypto_caam_jr@sta/crypto_caam_jr_caam_jr_hw.c.o.d' -o 'drivers/a715181@@tmp_rte_crypto_caam_jr@sta/crypto_caam_jr_caam_jr_hw.c.o' -c ../drivers/crypto/caam_jr/caam_jr_hw.c
In file included from ../drivers/crypto/caam_jr/caam_jr_hw.c:16:
../drivers/crypto/caam_jr/caam_jr_pvt.h:139:25: error: field 'encap_pdb' with variable sized type 'struct ipsec_encap_pdb' not at the end of a struct or class is a GNU extension [-Werror,-Wgnu-variable-sized-type-not-at-end]
struct ipsec_encap_pdb encap_pdb;
^
1 error generated.
ninja: build stopped: subcommand failed.
==== End log output ====
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.3
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28405/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-17 5:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 5:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-17 5:38 dpdklab
2023-11-17 5:36 dpdklab
2023-11-17 5:15 dpdklab
2023-11-17 5:05 dpdklab
2023-11-17 5:01 dpdklab
2023-11-17 5:00 dpdklab
2023-11-17 5:00 dpdklab
2023-11-17 4:58 dpdklab
2023-11-17 4:57 dpdklab
2023-11-17 4:57 dpdklab
2023-11-17 4:55 dpdklab
2023-11-17 4:54 dpdklab
2023-11-17 4:52 dpdklab
2023-11-17 4:51 dpdklab
2023-11-17 4:51 dpdklab
2023-11-17 4:51 dpdklab
2023-11-17 4:50 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=6556fb65.050a0220.163f4.1d1fSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=stephen@networkplumber.org \
--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).