From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: |FAILURE| pw130663-130674 [PATCH] [12/12] crypto/dpaa2_sec: add supp
Date: Wed, 23 Aug 2023 04:19:48 -0700 (PDT) [thread overview]
Message-ID: <64e5eb54.170a0220.e38ab.5b3bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/130674
_Testing issues_
Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Wednesday, August 23 2023 07:08:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:971d2b57972919527e27ed683032a71864a2eb56
130663-130674 --> testing fail
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04 | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Alpine | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Fedora 37 | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
==== 20 line log output for Fedora 38 (dpdk_meson_compile): ====
../drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:3241:35: error: array subscript 50 is outside array bounds of 'uint8_t[48]' {aka 'unsigned char[48]'} [-Werror=array-bounds=]
3241 | uh->dst_port = rte_cpu_to_be_16(dport);
| ^~
../drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:3166:25: note: at offset 400 into object 'hdr' of size 48
3166 | uint8_t hdr[48] = {};
| ^~~
../drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:3242:35: error: array subscript 50 is outside array bounds of 'uint8_t[48]' {aka 'unsigned char[48]'} [-Werror=array-bounds=]
3242 | uh->dgram_len = 0;
| ^~
../drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:3166:25: note: at offset 400 into object 'hdr' of size 48
3166 | uint8_t hdr[48] = {};
| ^~~
../drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:3243:35: error: array subscript 50 is outside array bounds of 'uint8_t[48]' {aka 'unsigned char[48]'} [-Werror=array-bounds=]
3243 | uh->dgram_cksum = 0;
| ^~
../drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:3166:25: note: at offset 400 into object 'hdr' of size 48
3166 | uint8_t hdr[48] = {};
| ^~~
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27426/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-23 11:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 11:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-23 12:27 dpdklab
2023-08-23 11:40 dpdklab
2023-08-23 11:38 dpdklab
2023-08-23 11:37 dpdklab
2023-08-23 11:37 dpdklab
2023-08-23 11:36 dpdklab
2023-08-23 11:36 dpdklab
2023-08-23 11:36 dpdklab
2023-08-23 11:36 dpdklab
2023-08-23 11:35 dpdklab
2023-08-23 11:33 dpdklab
2023-08-23 11:33 dpdklab
2023-08-23 11:33 dpdklab
2023-08-23 11:33 dpdklab
2023-08-23 11:33 dpdklab
2023-08-23 11:33 dpdklab
2023-08-23 11:33 dpdklab
2023-08-23 11:30 dpdklab
2023-08-23 11:30 dpdklab
2023-08-23 11:24 dpdklab
2023-08-23 11:20 dpdklab
2023-08-23 11:20 dpdklab
2023-08-23 11:20 dpdklab
2023-08-23 11:19 dpdklab
2023-08-23 11:19 dpdklab
2023-08-23 11:19 dpdklab
2023-08-23 11:18 dpdklab
2023-08-23 11:17 dpdklab
2023-08-23 11:16 dpdklab
2023-08-23 11:16 dpdklab
2023-08-23 11:15 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=64e5eb54.170a0220.e38ab.5b3bSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=hemant.agrawal@nxp.com \
--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).