From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Qi Zhang <qi.z.zhang@intel.com>
Subject: |FAILURE| [GIT MASTER] 5acec4b4f9488d2d4619340fd1045410a4df52a0
Date: Thu, 28 Sep 2023 17:54:26 -0700 (PDT) [thread overview]
Message-ID: <65162042.4a0a0220.f1df9.a41aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: dpdk-next-net-intel
5acec4b4f9488d2d4619340fd1045410a4df52a0 --> testing fail
Test environment and result as below:
+---------------------+--------------------+
| Environment | dpdk_meson_compile |
+=====================+====================+
| FreeBSD 13 | FAIL |
+---------------------+--------------------+
| Debian Bullseye | PASS |
+---------------------+--------------------+
| Debian Buster | PASS |
+---------------------+--------------------+
| CentOS Stream 9 | PASS |
+---------------------+--------------------+
| Fedora 38 | FAIL |
+---------------------+--------------------+
| Fedora 37 | FAIL |
+---------------------+--------------------+
| openSUSE Leap 15 | PASS |
+---------------------+--------------------+
| RHEL8 | PASS |
+---------------------+--------------------+
| Ubuntu 20.04 | PASS |
+---------------------+--------------------+
| CentOS Stream 8 | PASS |
+---------------------+--------------------+
| Ubuntu 22.04 | PASS |
+---------------------+--------------------+
| Windows Server 2019 | PASS |
+---------------------+--------------------+
==== 20 line log output for Fedora 37 (dpdk_meson_compile): ====
| ^~~~~~~~~~~~~~~
In function '_mm256_loadu_si256',
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 'cpfl_fxp_parse_pattern' at ../drivers/net/cpfl/cpfl_flow_engine_fxp.c:184:3,
inlined from 'cpfl_fxp_parse_pattern_action' at ../drivers/net/cpfl/cpfl_flow_engine_fxp.c:545:7:
/usr/lib/gcc/x86_64-redhat-linux/12/include/avxintrin.h:929:10: error: array subscript '__m256i_u[2]' is partly outside array bounds of 'const void[76]' [-Werror=array-bounds]
929 | return *__P;
| ^~~~
../drivers/net/cpfl/cpfl_flow_engine_fxp.c: In function 'cpfl_fxp_parse_pattern_action':
../drivers/net/cpfl/cpfl_flow_engine_fxp.c:503:36: note: at offset [149, 213] into object 'pr_action' of size 76
503 | struct cpfl_flow_pr_action pr_action = { 0 };
| ^~~~~~~~~
../drivers/net/cpfl/cpfl_flow_engine_fxp.c:503:36: note: at offset [149, 213] into object 'pr_action' of size 76
../drivers/net/cpfl/cpfl_flow_parser.h:188:17: note: at offset [11, 64] into object 'cpfl_flow_pr_fv' of size 64
188 | uint8_t cpfl_flow_pr_fv[CPFL_MAX_SEM_FV_KEY_SIZE];
| ^~~~~~~~~~~~~~~
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
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
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.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 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.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/tarballs/26295/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-29 0:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 0:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-29 1:54 dpdklab
2023-09-29 1:51 dpdklab
2023-09-29 1:47 dpdklab
2023-09-29 1:45 dpdklab
2023-09-29 1:42 dpdklab
2023-09-29 1:35 dpdklab
2023-09-29 1:24 dpdklab
2023-09-29 1:02 dpdklab
2023-09-29 1:02 dpdklab
2023-09-29 0:56 dpdklab
2023-09-29 0:54 dpdklab
2023-09-29 0:54 dpdklab
2023-09-29 0:54 dpdklab
2023-09-29 0:54 dpdklab
2023-09-29 0:54 dpdklab
2023-09-29 0:54 dpdklab
2023-09-29 0:49 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=65162042.4a0a0220.f1df9.a41aSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=qi.z.zhang@intel.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).