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, 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] 45f04d88ae8fa6217812abdaa623d66b05fc7b6a
Date: Fri, 05 Jan 2024 03:44:25 -0800 (PST)	[thread overview]
Message-ID: <6597eb99.050a0220.6d75a.673bSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: 21.11-staging

45f04d88ae8fa6217812abdaa623d66b05fc7b6a --> testing fail

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Fedora 38           | FAIL           |
+---------------------+----------------+
| Fedora 37           | FAIL           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+

==== 20 line log output for Fedora 37 (dpdk_unit_test): ====
inlined from 'vhost_crypto_process_one_req' at ../lib/vhost/vhost_crypto.c:1256:6,
inlined from 'rte_vhost_crypto_fetch_requests' at ../lib/vhost/vhost_crypto.c:1687:8:
/usr/lib/gcc/x86_64-redhat-linux/12/include/avxintrin.h:935:8: error: array subscript '__m256i_u[2]' is partly outside array bounds of 'void[72]' [-Werror=array-bounds]
935 |   *__P = __A;
|   ~~~~~^~~~~
../lib/vhost/vhost_crypto.c: In function 'rte_vhost_crypto_fetch_requests':
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [1, 65] into object 'req' of size 72
1178 |         struct virtio_crypto_op_data_req req;
|                                          ^~~
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [2, 72] into object 'req' of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [129, 193] into object 'req' of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [1, 65] into object 'req' of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [2, 72] into object 'req' of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [129, 193] into object 'req' of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [1, 65] into object 'req' of size 72
cc1: all warnings being treated as errors
[491/3069] Generating fib.sym_chk with a meson_exe.py custom command.
[492/3069] Compiling C object 'lib/76b5a35@@rte_port@sta/port_rte_port_ras.c.o'.
[493/3069] Compiling C object 'lib/76b5a35@@rte_port@sta/port_rte_port_ring.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.3

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.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/tarballs/27569/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-05 11:44 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 11:44 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-05 13:43 dpdklab
2024-01-05 13:29 dpdklab
2024-01-05 12:10 dpdklab
2024-01-05 12:08 dpdklab
2024-01-05 12:07 dpdklab
2024-01-05 12:05 dpdklab
2024-01-05 12:04 dpdklab
2024-01-05 12:03 dpdklab
2024-01-05 11:58 dpdklab
2024-01-05 11:58 dpdklab
2024-01-05 11:57 dpdklab
2024-01-05 11:57 dpdklab
2024-01-05 11:57 dpdklab
2024-01-05 11:57 dpdklab
2024-01-05 11:56 dpdklab
2024-01-05 11:55 dpdklab
2024-01-05 11:55 dpdklab
2024-01-05 11:55 dpdklab
2024-01-05 11:52 dpdklab
2024-01-05 11:51 dpdklab
2024-01-05 11:47 dpdklab
2024-01-05 11:46 dpdklab
2024-01-05 11:46 dpdklab
2024-01-05 11:46 dpdklab
2024-01-05 11:45 dpdklab
2024-01-05 11:45 dpdklab
2024-01-05 11:44 dpdklab
2024-01-05 11:44 dpdklab
2024-01-05 11:44 dpdklab
2024-01-05 11:43 dpdklab
2024-01-05 11:43 dpdklab
2024-01-05 11:43 dpdklab
2024-01-05 11:43 dpdklab
2024-01-05 11:42 dpdklab
2024-01-05 11:41 dpdklab
2024-01-05 11:41 dpdklab
2022-03-01  6:08 dpdklab
2022-02-12  6:08 dpdklab
2022-02-07 10:04 dpdklab
2022-01-28  7:39 dpdklab
2022-01-27 17:15 dpdklab
2022-01-27  7:37 dpdklab
2022-01-21 16:32 dpdklab
2022-01-21  8:20 dpdklab
2022-01-20  8:18 dpdklab
2022-01-14  6:09 dpdklab
2021-11-30 19:39 dpdklab
2021-11-30 19:38 dpdklab
2021-11-30 19:22 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=6597eb99.050a0220.6d75a.673bSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).