automatic DPDK test reports
 help / color / mirror / Atom feed
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:33:55 -0700 (PDT)	[thread overview]
Message-ID: <64e5eea3.0d0a0220.e19ef.5c84SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-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_unit_test |
+=====================+================+
| CentOS Stream 9     | FAIL           |
+---------------------+----------------+
| Debian Bullseye     | FAIL           |
+---------------------+----------------+
| Debian Buster       | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Fedora 37           | FAIL           |
+---------------------+----------------+
| Ubuntu 20.04        | FAIL           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | FAIL           |
+---------------------+----------------+
| openSUSE Leap 15    | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+

==== 20 line log output for Ubuntu 22.04 (dpdk_unit_test): ====
../drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:3166:25: note: while referencing 'hdr'
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: while referencing 'hdr'
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: while referencing 'hdr'
3166 |                 uint8_t hdr[48] = {};
|                         ^~~
cc1: all warnings being treated as errors
[2155/2704] Compiling C object 'drivers/a715181@@tmp_rte_crypto_scheduler@sta/crypto_scheduler_scheduler_roundrobin.c.o'.
[2156/2704] Generating rte_crypto_openssl.pmd.c with a custom command.
[2157/2704] Generating rte_crypto_octeontx.sym_chk with a meson_exe.py custom command.
ninja: build stopped: subcommand failed.
==== End log output ====

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

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 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

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/

             reply	other threads:[~2023-08-23 11:34 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23 11:33 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: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: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=64e5eea3.0d0a0220.e19ef.5c84SMTPIN_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).