automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, thomas@monjalon.net
Cc: dpdk_sw_eng@intel.com, npg.sw.core.tools.prc@intel.com
Subject: [dpdk-test-report] |FAILURE| dpdk-next-net daily Intel builds
Date: 18 Nov 2022 07:47:01 -0800	[thread overview]
Message-ID: <5f0cd1$m7fe41@fmsmga002-auth.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 11413 bytes --]


Test-Label: Intel-compilation
Test-Status: FAILURE
_Compilation issues_


commit fe11380c7ae68adbc67fcac7f1e9cdf6c4b5295f
Author: Chaoyong He <chaoyong.he@corigine.com>
Date:   Fri Nov 18 09:44:08 2022 +0800

    net/nfp: fix Rx descriptor DMA address for VNIC

DPDK git Repo: dpdk-next-net 


Meson Build Summary: 27 Builds Done, 26 Successful, 1 Failures, 0 Blocked

+--------------+------------+--------------+------------+------------+-----------+----------+------------+
| os           | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document | gcc-16byte |
+--------------+------------+--------------+------------+------------+-----------+----------+------------+
| FC36-64      | pass       | pass         |            |            |           |          |            |
| FreeBSD13-64 | pass       | pass         |            | pass       | pass      |          |            |
| RHEL86-64    | pass       | pass         |            | pass       | pass      |          |            |
| SUSE15-64    | pass       | pass         |            |            |           |          |            |
| RHEL90-64    | pass       |              |            |            |           |          |            |
| UB2004-64    | pass       | pass         |            |            |           | pass     |            |
| UB2204-32    | pass       |              |            |            |           |          |            |
| UB2204-64N   | pass       |              |            | pass       |           |          |            |
| UB2204-64    | pass       | pass         |            |            |           | pass     | pass       |
| CentOS79-64  | pass       |              |            |            |           |          |            |
| RHEL86-64Rt  | pass       | fail         |            |            |           |          |            |
| UB2210-64    | pass       |              |            |            |           |          |            |
+--------------+------------+--------------+------------+------------+-----------+----------+------------+

Comments: 
Because of DPDK bug (https://bugs.dpdk.org/show_bug.cgi?id=928),
All the dpdk-next-* branch add `Ddisable_drivers=event/cnxk` option when build with ICC complier. 
 
Test environment and configuration as below:


OS: FC36-64
	Kernel Version: 5.17.7-300.fc36.x86_64
	GCC Version: gcc (GCC) 12.1.1 20220507 (Red Hat 12.1.1-1)
	Clang Version: 14.0.0 (Fedora 14.0.0-1.fc36)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang

OS: FreeBSD13-64
	Kernel Version: 13.1-RELEASE
	GCC Version: gcc (FreeBSD Ports Collection) 10.3.0
	Clang Version: 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a303)
	x86_64-native-bsdapp-gcc
	x86_64-native-bsdapp-clang
	x86_64-native-bsdapp-gcc+shared
	x86_64-native-bsdapp-gcc+debug

OS: RHEL86-64
	Kernel Version: 4.18.0-372.9.1.el8.x86_64
	GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-13)
	Clang Version: 14.0.0 (Red Hat 14.0.0-1.module_el8.7.0+1142+5343df54)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc+shared
	x86_64-native-linuxapp-gcc+debug

OS: SUSE15-64
	Kernel Version: 5.14.21-150400.22-default
	GCC Version: gcc (SUSE Linux) 7.5.0
	Clang Version: 11.0.1
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc

OS: RHEL90-64
	Kernel Version: 5.14.0-70.13.1.el9_0.x86_64
	GCC Version: gcc (GCC) 11.2.1 20220127 (Red Hat 11.2.1-9)
	Clang Version: 13.0.1 (Red Hat 13.0.1-1.el9)
	x86_64-native-linuxapp-gcc

OS: UB2004-64
	Kernel Version: 5.8.0-48-generic
	GCC Version: gcc (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
	Clang Version: 10.0.0-4ubuntu1
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-doc

OS: UB2204-32
	Kernel Version: 5.15.0-25-generic
	GCC Version: gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
	Clang Version: NA
	i686-native-linuxapp-gcc

OS: UB2204-64N
	Kernel Version: 5.17.5-051705-generic
	GCC Version: gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
	Clang Version: 14.0.0-1ubuntu1
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-gcc+shared

OS: UB2204-64
	Kernel Version: 5.15.0-25-generic
	GCC Version: gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
	Clang Version: 14.0.0-1ubuntu1
	x86_64-native-linuxapp-gcc+16byte
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-doc

OS: CentOS79-64
	Kernel Version: 3.10.0-1160.el7.x86_64
	GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
	Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
	x86_64-native-linuxapp-gcc

OS: RHEL86-64Rt
	Kernel Version: 4.18.0-372.9.1.rt7.166.el8.x86_64
	GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-13)
	Clang Version: 14.0.0 (Red Hat 14.0.0-1.module_el8.7.0+1142+5343df54)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang

OS: UB2210-64
	Kernel Version: 5.19.0-21-generic
	GCC Version: gcc (Ubuntu 12.2.0-3ubuntu1) 12.2.0
	Clang Version: 15.0.2-1
	x86_64-native-linuxapp-gcc



*Build Failed #1:
OS: RHEL86-64Rt
Target: x86_64-native-linuxapp-clang
FAILED: drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_rx_cn10k_rx_96_111_vec_mseg.c.o 
clang -Idrivers/libtmp_rte_net_cnxk.a.p -Idrivers -I../drivers -Idrivers/net/cnxk -I../drivers/net/cnxk -Ilib/ethdev -I../lib/ethdev -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/meter -I../lib/meter -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/pci -I../lib/pci -Idrivers/bus/vdev -I../drivers/bus/vdev -Ilib/cryptodev -I../lib/cryptodev -Ilib/rcu -I../lib/rcu -Ilib/eventdev -I../lib/eventdev -Ilib/hash -I../lib/hash -Ilib/timer -I../lib/timer -Ilib/security -I../lib/security -Idrivers/common/cnxk -I../drivers/common/cnxk -Idrivers/mempool/cnxk -I../drivers/mempool/cnxk -fcolor-diagnostics -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -O3 -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-address-of-packed-member -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=native -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -flax-vector-conversions -Wno-strict-aliasing -DRTE_LOG_DEFAULT_LOGTYPE=pmd.net.cnxk -MD -MQ drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_rx_cn10k_rx_96_111_vec_mseg.c.o -MF drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_rx_cn10k_rx_96_111_vec_mseg.c.o.d -o drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_rx_cn10k_rx_96_111_vec_mseg.c.o -c ../drivers/net/cnxk/rx/cn10k/rx_96_111_vec_mseg.c
*** stack smashing detected ***: <unknown> terminated
PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace, preprocessed source, and associated run script.
Stack dump:
0.	Program arguments: clang -Idrivers/libtmp_rte_net_cnxk.a.p -Idrivers -I../drivers -Idrivers/net/cnxk -I../drivers/net/cnxk -Ilib/ethdev -I../lib/ethdev -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/meter -I../lib/meter -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/pci -I../lib/pci -Idrivers/bus/vdev -I../drivers/bus/vdev -Ilib/cryptodev -I../lib/cryptodev -Ilib/rcu -I../lib/rcu -Ilib/eventdev -I../lib/eventdev -Ilib/hash -I../lib/hash -Ilib/timer -I../lib/timer -Ilib/security -I../lib/security -Idrivers/common/cnxk -I../drivers/common/cnxk -Idrivers/mempool/cnxk -I../drivers/mempool/cnxk -fcolor-diagnostics -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -O3 -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-address-of-packed-member -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=native -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -flax-vector-conversions -Wno-strict-aliasing -DRTE_LOG_DEFAULT_LOGTYPE=pmd.net.cnxk -MD -MQ drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_rx_cn10k_rx_96_111_vec_mseg.c.o -MF drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_rx_cn10k_rx_96_111_vec_mseg.c.o.d -o drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_rx_cn10k_rx_96_111_vec_mseg.c.o -c ../drivers/net/cnxk/rx/cn10k/rx_96_111_vec_mseg.c
1.	/usr/lib64/clang/14.0.0/include/avx512vlintrin.h:6520:1: current parser token 'static'
Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it):
/lib64/libLLVM-14.so(_ZN4llvm3sys15PrintStackTraceERNS_11raw_ostreamEi+0x30)[0x7f49d6662490]
/lib64/libLLVM-14.so(_ZN4llvm3sys17RunSignalHandlersEv+0x34)[0x7f49d6660034]
/lib64/libLLVM-14.so(_ZN4llvm3sys15CleanupOnSignalEm+0x129)[0x7f49d66609d9]
/lib64/libLLVM-14.so(+0xac4738)[0x7f49d6578738]
/lib64/libpthread.so.0(+0x12ce0)[0x7f49df26dce0]
/lib64/libc.so.6(gsignal+0x10f)[0x7f49d4e0da4f]
/lib64/libc.so.6(abort+0x127)[0x7f49d4de0db5]
/lib64/libc.so.6(+0x91057)[0x7f49d4e50057]
/lib64/libc.so.6(+0x13f5b5)[0x7f49d4efe5b5]
/lib64/libc.so.6(+0x13f568)[0x7f49d4efe568]
/lib64/libclang-cpp.so.14(+0x110b221)[0x7f49dca15221]
[0x7ffdda8935b0]
clang-14: error: clang frontend command failed with exit code 134 (use -v to see invocation)
clang version 14.0.0 (Red Hat 14.0.0-1.module_el8.7.0+1142+5343df54)
Target: x86_64-redhat-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
clang-14: note: diagnostic msg: 
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang-14: note: diagnostic msg: /tmp/rx_96_111_vec_mseg-b0697f.c
clang-14: note: diagnostic msg: /tmp/rx_96_111_vec_mseg-b0697f.sh
clang-14: note: diagnostic msg: 

********************
[1360/3394] Compiling C object drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_rx_cn10k_rx_80_95_mseg.c.o
[1361/3394] Compiling C object drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_rx_cn10k_rx_96_111_mseg.c.o
[1362/3394] Compiling C object drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_rx_cn10k_rx_112_127_vec_mseg.c.o
[1363/3394] Compiling C object drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_rx_cn10k_rx_112_127_mseg.c.o
[1364/3394] Compiling C object drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_tx_cn10k_tx_32_47.c.o
[1365/3394] Compiling C object drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_tx_cn10k_tx_16_31.c.o
[1366/3394] Compiling C object drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_tx_cn10k_tx_48_63.c.o
[1367/3394] Compiling C object drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_tx_cn10k_tx_64_79.c.o
[1368/3394] Compiling C object drivers/libtmp_rte_net_cnxk.a.p/net_cnxk_tx_cn10k_tx_80_95.c.o
ninja: build stopped


DPDK STV team

             reply	other threads:[~2022-11-18 15:47 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 15:47 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-09 15:56 sys_stv
2023-06-09 15:01 sys_stv
2023-06-09 14:43 sys_stv
2023-05-16 22:28 sys_stv
2023-05-15 22:24 sys_stv
2023-04-27  6:48 sys_stv
2023-03-02 16:56 sys_stv
2023-03-02 15:47 sys_stv
2023-01-09 22:06 sys_stv
2022-12-06 14:28 sys_stv
2022-10-27  9:09 sys_stv
2022-10-27  2:43 sys_stv
2022-10-27  1:15 sys_stv
2022-10-26  6:07 sys_stv
2022-10-25 22:04 sys_stv
2022-10-20  7:19 sys_stv
2022-10-13 21:56 sys_stv
2022-10-07 10:49 sys_stv
2022-09-21 15:19 sys_stv
2022-09-21  9:30 sys_stv
2022-09-20  6:40 sys_stv
2022-09-19  1:58 sys_stv
2022-09-18 21:40 sys_stv
2022-09-14  4:11 sys_stv
2022-09-13 21:43 sys_stv
2022-09-10 21:43 sys_stv
2022-09-08 10:59 sys_stv
2022-09-07 21:43 sys_stv
2022-09-07  8:56 sys_stv
2022-09-06 21:42 sys_stv
2022-08-08 21:42 sys_stv
2022-06-06  2:27 sys_stv
2022-06-01 21:38 sys_stv
2022-05-31 21:38 sys_stv
2022-05-18 21:40 sys_stv
2022-05-17 21:40 sys_stv
2022-05-17 10:10 sys_stv
2022-05-16 21:50 sys_stv
2022-05-06 21:43 sys_stv
2022-01-28 10:53 sys_stv
2022-01-28  9:30 sys_stv
2022-01-28  4:53 sys_stv
2022-01-27 22:53 sys_stv
2022-01-27 16:53 sys_stv
2022-01-27 10:53 sys_stv
2022-01-27  5:42 sys_stv
2022-01-27  4:42 sys_stv
2022-01-27  3:32 sys_stv
2022-01-26 22:42 sys_stv
2022-01-26 16:42 sys_stv
2022-01-26  4:43 sys_stv
2022-01-26  3:54 sys_stv
2022-01-25 16:42 sys_stv
2022-01-25  7:32 sys_stv

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='5f0cd1$m7fe41@fmsmga002-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=dpdk_sw_eng@intel.com \
    --cc=npg.sw.core.tools.prc@intel.com \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).