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, Vamsi Attunuru <vattunuru@marvell.com>
Subject: |FAILURE| pw132488-132490 [PATCH] [3/3] net/octeon_ep: add new fastp
Date: Wed, 11 Oct 2023 07:41:33 -0700 (PDT)	[thread overview]
Message-ID: <6526b41d.c80a0220.130f8.02caSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/132490

_Testing issues_

Submitter: Vamsi Attunuru <vattunuru@marvell.com>
Date: Wednesday, October 11 2023 01:50:54 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a3d2c6974f915eb9cb3d015afdc4cc72537a6159

132488-132490 --> testing fail

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian Buster       | PASS           |
+---------------------+----------------+
| Fedora 37           | FAIL           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| openSUSE Leap 15    | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+

==== 20 line log output for Fedora 37 (dpdk_unit_test): ====
inlined from 'rte_mov32' at ../lib/eal/x86/include/rte_memcpy.h:346:9,
inlined from 'rte_memcpy_generic' at ../lib/eal/x86/include/rte_memcpy.h:475:4,
inlined from 'rte_memcpy' at ../lib/eal/x86/include/rte_memcpy.h:868:10,
inlined from 'post_iqcmd' at ../drivers/net/octeon_ep/otx_ep_rxtx.c:505:2,
inlined from 'otx_ep_send_data' at ../drivers/net/octeon_ep/otx_ep_rxtx.c:530:8,
inlined from 'otx_ep_xmit_pkts' at ../drivers/net/octeon_ep/otx_ep_rxtx.c:660:7:
/usr/lib/gcc/x86_64-redhat-linux/12/include/avxintrin.h:929:10: error: array subscript [2, 4] is outside array bounds of 'const void[64]' [-Werror=array-bounds]
929 |   return *__P;
|          ^~~~
../drivers/net/octeon_ep/otx_ep_rxtx.c: In function 'otx_ep_xmit_pkts':
../drivers/net/octeon_ep/otx_ep_rxtx.c:598:33: note: at offset [129, 193] into object 'iqcmd' of size 64
598 |         struct otx_ep_instr_64B iqcmd;
|                                 ^~~~~
../drivers/net/octeon_ep/otx_ep_rxtx.c:598:33: note: at offset [129, 193] into object 'iqcmd' of size 64
../drivers/net/octeon_ep/otx_ep_rxtx.c:598:33: note: at offset [1, 64] into object 'iqcmd' of size 64
cc1: all warnings being treated as errors
[1772/2709] Generating symbol file 'drivers/a715181@@rte_net_octeontx@sha/librte_net_octeontx.so.24.0.symbols'.
[1773/2709] Compiling C object 'drivers/a715181@@tmp_rte_net_octeon_ep@sta/net_octeon_ep_otx_ep_vf.c.o'.
[1774/2709] Generating rte_common_cnxk.sym_chk with a meson_exe.py custom command.
ninja: build stopped: subcommand failed.
==== End log output ====

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

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

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

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

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

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

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

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/27893/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2023-10-11 14:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11 14:41 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-11 11:03 dpdklab
2023-10-11 10:38 dpdklab
2023-10-11  9:54 dpdklab
2023-10-11  9:52 dpdklab
2023-10-11  9:52 dpdklab
2023-10-11  9:51 dpdklab
2023-10-11  9:51 dpdklab
2023-10-11  9:51 dpdklab
2023-10-11  9:50 dpdklab
2023-10-11  9:49 dpdklab
2023-10-11  9:48 dpdklab
2023-10-11  9:48 dpdklab
2023-10-11  9:47 dpdklab
2023-10-11  9:45 dpdklab
2023-10-11  9:44 dpdklab
2023-10-11  9:44 dpdklab
2023-10-11  9:43 dpdklab
2023-10-11  9:43 dpdklab
2023-10-11  9:42 dpdklab
2023-10-11  9:39 dpdklab
2023-10-11  9:37 dpdklab
2023-10-11  9:37 dpdklab
2023-10-11  9:35 dpdklab
2023-10-11  9:31 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=6526b41d.c80a0220.130f8.02caSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=vattunuru@marvell.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).