From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] 9dae7a15aea76313c592c11db44e1386e85f86fe
Date: Tue, 4 Apr 2023 04:46:22 +0000 (UTC) [thread overview]
Message-ID: <20230404044622.785546012C@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
_Testing issues_
Branch: tags/v22.11
9dae7a15aea76313c592c11db44e1386e85f86fe --> testing fail
Test environment and result as below:
+--------------------+----------------+
| Environment | dpdk_unit_test |
+====================+================+
| Debian Buster | PASS |
+--------------------+----------------+
| CentOS Stream 9 | FAIL |
+--------------------+----------------+
| Debian 11 (Buster) | PASS |
+--------------------+----------------+
| Debian Bullseye | PASS |
+--------------------+----------------+
| Fedora 36 | PASS |
+--------------------+----------------+
| CentOS Stream 8 | PASS |
+--------------------+----------------+
| RHEL 7 | PASS |
+--------------------+----------------+
| Ubuntu 20.04 (ARM) | PASS |
+--------------------+----------------+
| Ubuntu 22.04 | PASS |
+--------------------+----------------+
| Ubuntu 20.04 | PASS |
+--------------------+----------------+
| RHEL8 | PASS |
+--------------------+----------------+
| openSUSE Leap 15 | PASS |
+--------------------+----------------+
==== 20 line log output for CentOS Stream 9 (dpdk_unit_test): ====
ccache cc -Idrivers/a715181@@tmp_rte_crypto_openssl@sta -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/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/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 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -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 -Wwr
ite-strings -Wno-address-of-packed-member -Wno-packed-not-aligned -Wno-missing-field-initializers -Wno-zero-length-bounds -D_GNU_SOURCE -fPIC -march=armv8.1-a+crc+crypto -mcpu=thunderx2t99 -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DRTE_LOG_DEFAULT_LOGTYPE=pmd.crypto.openssl -MD -MQ 'drivers/a715181@@tmp_rte_crypto_openssl@sta/crypto_openssl_rte_openssl_pmd.c.o' -MF 'drivers/a715181@@tmp_rte_crypto_openssl@sta/crypto_openssl_rte_openssl_pmd.c.o.d' -o 'drivers/a715181@@tmp_rte_crypto_openssl@sta/crypto_openssl_rte_openssl_pmd.c.o' -c ../drivers/crypto/openssl/rte_openssl_pmd.c
In file included from ../lib/eal/arm/include/rte_memcpy.h:9,
from ../lib/mempool/rte_mempool.h:48,
from ../lib/mbuf/rte_mbuf.h:38,
from ../lib/cryptodev/rte_crypto.h:20,
from ../lib/cryptodev/rte_cryptodev.h:23,
from ../drivers/crypto/openssl/rte_openssl_pmd.c:7:
In function 'openssl_set_session_auth_parameters',
inlined from 'openssl_set_session_parameters' at ../drivers/crypto/openssl/rte_openssl_pmd.c:826:9:
../lib/eal/arm/include/rte_memcpy_64.h:364:33: error: 'memcpy' forming offset [4, 8] is out of the bounds [0, 4] [-Werror=array-bounds]
364 | #define rte_memcpy(d, s, n) memcpy((d), (s), (n))
| ^~~~~~~~~~~~~~~~~~~~~
../drivers/crypto/openssl/rte_openssl_pmd.c:699:17: note: in expansion of macro 'rte_memcpy'
699 | rte_memcpy(algo_name, algo, (sizeof(algo)+1));
| ^~~~~~~~~~
cc1: all warnings being treated as errors
[2476/3435] Generating rte_crypto_scheduler.sym_chk with a meson_exe.py custom command.
[2477/3435] Generating rte_crypto_virtio.pmd.c with a custom command.
[2478/3435] Compiling C object 'drivers/a715181@@tmp_rte_compress_mlx5@sta/compress_mlx5_mlx5_compress.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====
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
Debian 11 (Buster)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 36
Kernel: Container Host Kernel
Compiler: gcc 12.2.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
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 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
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)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/24133/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-04 4:46 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 4:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-16 5:38 dpdklab
2023-04-16 5:36 dpdklab
2023-04-15 10:29 dpdklab
2023-04-15 7:10 dpdklab
2023-04-14 6:02 dpdklab
2023-04-14 5:31 dpdklab
2023-04-13 5:35 dpdklab
2023-04-13 5:23 dpdklab
2023-04-12 5:35 dpdklab
2023-04-11 5:16 dpdklab
2023-04-10 4:48 dpdklab
2023-04-09 5:02 dpdklab
2023-04-08 5:09 dpdklab
2023-04-07 5:12 dpdklab
2023-04-06 12:10 dpdklab
2023-04-05 4:32 dpdklab
2023-04-05 4:23 dpdklab
2023-04-05 4:15 dpdklab
2023-04-03 4:42 dpdklab
2023-04-02 4:50 dpdklab
2023-04-01 4:54 dpdklab
2023-03-31 18:52 dpdklab
2023-03-31 18:41 dpdklab
2023-03-29 4:45 dpdklab
2023-03-29 4:40 dpdklab
2023-03-29 4:31 dpdklab
2023-03-29 4:28 dpdklab
2023-03-16 5:02 dpdklab
2023-02-23 5:43 dpdklab
2023-02-23 5:34 dpdklab
2023-02-22 5:33 dpdklab
2023-02-19 5:44 dpdklab
2023-02-19 5:31 dpdklab
2023-02-19 5:28 dpdklab
2023-02-11 5:31 dpdklab
2023-02-11 5:31 dpdklab
2023-02-11 5:27 dpdklab
2023-02-10 5:34 dpdklab
2023-02-10 5:18 dpdklab
2023-01-22 5:23 dpdklab
2023-01-19 5:24 dpdklab
2023-01-13 5:43 dpdklab
2023-01-13 5:39 dpdklab
2023-01-13 5:24 dpdklab
2023-01-11 15:08 dpdklab
2023-01-11 5:41 dpdklab
2023-01-10 5:30 dpdklab
2023-01-10 5:27 dpdklab
2023-01-07 5:43 dpdklab
2023-01-07 5:27 dpdklab
2023-01-05 5:24 dpdklab
2023-01-02 5:23 dpdklab
2022-12-29 6:46 dpdklab
2022-12-29 6:46 dpdklab
2022-12-29 6:46 dpdklab
2022-12-29 6:45 dpdklab
2022-12-29 6:45 dpdklab
2022-12-29 6:45 dpdklab
2022-12-29 5:22 dpdklab
2022-12-28 5:42 dpdklab
2022-12-28 5:38 dpdklab
2022-12-26 7:02 dpdklab
2022-12-26 7:02 dpdklab
2022-12-26 7:02 dpdklab
2022-12-26 7:01 dpdklab
2022-12-21 9:56 dpdklab
2022-12-21 9:55 dpdklab
2022-12-21 9:55 dpdklab
2022-12-21 9:52 dpdklab
2022-12-21 9:52 dpdklab
2022-12-21 9:52 dpdklab
2022-12-21 9:52 dpdklab
2022-12-20 7:11 dpdklab
2022-12-20 7:10 dpdklab
2022-12-20 7:07 dpdklab
2022-12-20 7:07 dpdklab
2022-12-20 7:07 dpdklab
2022-12-20 7:07 dpdklab
2022-12-20 6:40 dpdklab
2022-12-04 6:44 dpdklab
2022-12-04 6:43 dpdklab
2022-12-04 6:40 dpdklab
2022-12-04 6:34 dpdklab
2022-12-04 6:34 dpdklab
2022-12-04 6:33 dpdklab
2022-12-04 6:33 dpdklab
2022-12-04 6:32 dpdklab
2022-12-04 6:26 dpdklab
2022-12-04 5:30 dpdklab
2022-12-04 5:26 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=20230404044622.785546012C@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).