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-master daily Intel builds
Date: 04 Jun 2019 18:41:16 -0700	[thread overview]
Message-ID: <ee68f5$740hsh@orsmga001.jf.intel.com> (raw)

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

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


commit 7f9f46d6cef5b03681a3935b9a18378e08ca6f62
Author: Xiaolong Ye <xiaolong.ye@intel.com>
Date:   Thu May 16 15:28:56 2019 +0800

    ring: remove unnecessary forward declaration

Git Repo  :dpdk-master
Build Summary: 22 Builds Done, 22 Successful, 0 Failures

Meson Summary: 8 Builds Done, 6 Successful, 2 Failures



Test environment and configuration as below:

**Make Build**


OS: RHEL76-64
	Kernel Version: 3.10.0-957.el7.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)
	Clang Version: NA
	x86_64-native-linuxapp-gcc


OS: CENTOS76-64
	Kernel Version: 3.10.0-957.10.1.el7.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)
	Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
	x86_64-native-linuxapp-gcc+shared
	x86_64-native-linuxapp-icc
	x86_64-native-linuxapp-gcc+debug
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang


OS: UB1804-64
	Kernel Version: 4.15.0-20-generic
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (Ubuntu 7.3.0-16ubuntu3) 7.3.0
	Clang Version: 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-icc
	x86_64-native-linuxapp-gcc


OS: UB1904-64
	Kernel Version: 5.0.0-13-generic
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (Ubuntu 8.3.0-6ubuntu1) 8.3.0
	Clang Version: 8.0.0-3 (tags/RELEASE_800/final)
	x86_64-native-linuxapp-gcc


OS: UB1604-32
	Kernel Version: 4.4.0-131-generic
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.11) 5.4.0 20160609
	Clang Version: 3.8.0-2ubuntu4 (tags/RELEASE_380/final)
	i686-native-linuxapp-gcc


OS: UB1604-64
	Kernel Version: 4.4.0-47-generic
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609
	Clang Version: 3.8.0-2ubuntu4 (tags/RELEASE_380/final)
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc


OS: RHEL75-64
	Kernel Version: 3.10.0-862.el7.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-28)
	Clang Version: NA
	x86_64-native-linuxapp-gcc


OS: FreeBSD12-64
	Kernel Version: 12.0-RC3
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz (2194.97-MHz K8-class CPU)
	GCC Version: gcc (FreeBSD Ports Collection) 7.3.0
	Clang Version: 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1)
	x86_64-native-bsdapp-gcc+debug
	x86_64-native-bsdapp-gcc+shared
	x86_64-native-bsdapp-gcc
	x86_64-native-bsdapp-clang


OS: SUSE15-64
	Kernel Version: 4.12.14-lp150.11-default
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (SUSE Linux) 7.3.1 20180323 [gcc-7-branch revision 258812]
	Clang Version: 5.0.1 (tags/RELEASE_501/final 312548)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang


OS: FD30-64
	Kernel Version: 5.0.9-301.fc30.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 9.1.1 20190503 (Red Hat 9.1.1-1)
	Clang Version: 8.0.0 (Fedora 8.0.0-1.fc30)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang


**Meson Build**


OS: CENTOS76-64
	Kernel Version: 3.10.0-957.10.1.el7.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)
	Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
	build-gcc-static
	build-gcc-shared
	build-clang-static
	build-clang-shared
	build-x86-default


OS: UB1804-64
	Kernel Version: 4.15.0-20-generic
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0
	Clang Version: 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
	x86_64-native-linuxapp-doc
	build-gcc-static
	build-gcc-shared
	build-clang-static
	build-clang-shared
	build-x86-default


OS: UB1604-32
	Kernel Version: 4.4.0-131-generic
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.11) 5.4.0 20160609
	Clang Version: 3.8.0-2ubuntu4 (tags/RELEASE_380/final)
	build-gcc-static
	build-gcc-shared
	build-clang-static
	build-clang-shared
	build-x86-default


OS: WIN10-64
	Kernel Version: N/A
	CPU info: N/A
	GCC Version: N/A
	Clang Version: Clang 8.0.0
	x86_64-windows-clang


OS: FreeBSD12-64
	Kernel Version: 12.0-RC3
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz (2194.98-MHz K8-class CPU)
	GCC Version: gcc (FreeBSD Ports Collection) 7.3.0
	Clang Version: 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1)
	build-gcc-static
	build-gcc-shared
	build-clang-static
	build-clang-shared
	build-x86-default


OS: SUSE15-64
	Kernel Version: 4.12.14-lp150.11-default
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (SUSE Linux) 7.3.1 20180323 [gcc-7-branch revision 258812]
	Clang Version: 5.0.1 (tags/RELEASE_501/final 312548)
	build-gcc-static
	build-gcc-shared
	build-clang-static
	build-clang-shared
	build-x86-default


OS: FD30-64
	Kernel Version: 5.0.9-301.fc30.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 9.1.1 20190503 (Red Hat 9.1.1-1)
	Clang Version: 8.0.0 (Fedora 8.0.0-1.fc30)
	build-gcc-static
	build-gcc-shared
	build-clang-static
	build-clang-shared
	build-x86-default

*Meson Failed Build #1:
OS: CENTOS76-64
Target:build-gcc-static
FAILED: drivers/a715181@@tmp_rte_pmd_aesni_mb@sta/crypto_aesni_mb_rte_aesni_mb_pmd.c.o 
gcc -Idrivers/a715181@@tmp_rte_pmd_aesni_mb@sta -Idrivers -I../drivers -Idrivers/crypto/aesni_mb -I../drivers/crypto/aesni_mb -Ilib/librte_cryptodev -I../lib/librte_cryptodev -I. -I../ -Iconfig -I../config -Ilib/librte_eal/common/include -I../lib/librte_eal/common/include -I../lib/librte_eal/linux/eal/include -Ilib/librte_eal/common -I../lib/librte_eal/common -Ilib/librte_eal/common/include/arch/x86 -I../lib/librte_eal/common/include/arch/x86 -Ilib/librte_eal -I../lib/librte_eal -Ilib/librte_kvargs -I../lib/librte_kvargs -Ilib/librte_mbuf -I../lib/librte_mbuf -Ilib/librte_mempool -I../lib/librte_mempool -Ilib/librte_ring -I../lib/librte_ring -Idrivers/bus/vdev -I../drivers/bus/vdev -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Werror -O3 -include rte_config.h -Wunused-parameter -Wsign-compare -Wcast-qual -fPIC -march=native -D_GNU_SOURCE -DALLOW_EXPERIMENTAL_API -MD -MQ 'drivers/a715181@@tmp_rte_pmd_aesni_mb@sta/crypto_aesni_mb_rte_aesni_mb_pmd.c.o' -MF 'drivers/a715181@@tmp_rte_pmd_aesni_mb@sta/crypto_aesni_mb_rte_aesni_mb_pmd.c.o.d' -o 'drivers/a715181@@tmp_rte_pmd_aesni_mb@sta/crypto_aesni_mb_rte_aesni_mb_pmd.c.o' -c ../drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c
../drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c: In function ‘aesni_mb_set_session_auth_parameters’:
../drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c:60:19: error: ‘hash_oneblock_fn’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
  (*one_block_hash)(opad_buf, opad);
                   ^
../drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c:107:19: note: ‘hash_oneblock_fn’ was declared here
  hash_one_block_t hash_oneblock_fn;
                   ^
cc1: all warnings being treated as errors
[1068/1674] Generating rte_pmd_aesni_gcm.pmd.c with a custom command.
[1069/1674] Compiling C object 'drivers/a715181@@tmp_rte_pmd_vmxnet3@sta/net_vmxnet3_vmxnet3_ethdev.c.o'.
[1070/1674] Compiling C object 'drivers/a715181@@tmp_rte_pmd_vmxnet3@sta/net_vmxnet3_vmxnet3_rxtx.c.o'.
[1071/1674] Compiling C object 'drivers/a715181@@tmp_rte_pmd_caam_jr@sta/crypto_caam_jr_caam_jr_hw.c.o'.
[1072/1674] Compiling C object 'drivers/a715181@@tmp_rte_pmd_virtio@sta/net_virtio_virtio_rxtx.c.o'.
ninja: build stopped: subcommand failed



*Meson Failed Build #2:
OS: FreeBSD12-64
Target:build-gcc-static
FAILED: examples/c590b3c@@dpdk-mp_server@exe/multi_process_client_server_mp_mp_server_main.c.o 
gcc -Iexamples/c590b3c@@dpdk-mp_server@exe -Iexamples -I../examples -Iexamples/multi_process/client_server_mp/mp_server -I../examples/multi_process/client_server_mp/mp_server -I../examples/multi_process/client_server_mp/mp_server/../shared -I. -I../ -Iconfig -I../config -Ilib/librte_eal/common/include -I../lib/librte_eal/common/include -I../lib/librte_eal/freebsd/eal/include -Ilib/librte_eal/common -I../lib/librte_eal/common -Ilib/librte_eal/common/include/arch/x86 -I../lib/librte_eal/common/include/arch/x86 -Ilib/librte_eal -I../lib/librte_eal -Ilib/librte_kvargs -I../lib/librte_kvargs -Ilib/librte_mempool -I../lib/librte_mempool -Ilib/librte_ring -I../lib/librte_ring -Ilib/librte_net -I../lib/librte_net -Ilib/librte_mbuf -I../lib/librte_mbuf -Ilib/librte_ethdev -I../lib/librte_ethdev -Ilib/librte_cmdline -I../lib/librte_cmdline -Ilib/librte_meter -I../lib/librte_meter -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Werror -O3 -include rte_config.h -Wunused-parameter -Wsign-compare -Wcast-qual -march=native -Wno-format-truncation -D_GNU_SOURCE -MD -MQ 'examples/c590b3c@@dpdk-mp_server@exe/multi_process_client_server_mp_mp_server_main.c.o' -MF 'examples/c590b3c@@dpdk-mp_server@exe/multi_process_client_server_mp_mp_server_main.c.o.d' -o 'examples/c590b3c@@dpdk-mp_server@exe/multi_process_client_server_mp_mp_server_main.c.o' -c ../examples/multi_process/client_server_mp/mp_server/main.c
In file included from ../examples/multi_process/client_server_mp/mp_server/main.c:14:0:
/usr/include/netinet/ip.h:71:17: error: field 'ip_src' has incomplete type
  struct in_addr ip_src,ip_dst; /* source and dest address */
                 ^~~~~~
/usr/include/netinet/ip.h:71:24: error: field 'ip_dst' has incomplete type
  struct in_addr ip_src,ip_dst; /* source and dest address */
                        ^~~~~~
/usr/include/netinet/ip.h:188:19: error: field 'ipt_addr' has incomplete type
    struct in_addr ipt_addr;
                   ^~~~~~~~
/usr/include/netinet/ip.h:223:17: error: field 'ippseudo_src' has incomplete type
  struct in_addr ippseudo_src; /* source internet address */
                 ^~~~~~~~~~~~
/usr/include/netinet/ip.h:224:17: error: field 'ippseudo_dst' has incomplete type
  struct in_addr ippseudo_dst; /* destination internet address */
                 ^~~~~~~~~~~~
[1190/1233] Linking target examples/dpdk-l3fwd-vf.
[1191/1233] Compiling C object 'examples/c590b3c@@dpdk-mp_server@exe/multi_process_client_server_mp_mp_server_init.c.o'.
[1192/1233] Compiling C object 'examples/c590b3c@@dpdk-mp_client@exe/multi_process_client_server_mp_mp_client_client.c.o'.
[1193/1233] Compiling C object 'examples/c590b3c@@dpdk-simple_mp@exe/multi_process_simple_mp_mp_commands.c.o'.
[1194/1233] Compiling C object 'examples/c590b3c@@dpdk-load_balancer@exe/load_balancer_runtime.c.o'.
ninja: build stopped: subcommand failed



DPDK STV team

             reply	other threads:[~2019-06-05  1:41 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05  1:41 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-07-05 21:52 sys_stv
2020-07-04 21:52 sys_stv
2020-07-03 22:47 sys_stv
2020-06-29 22:09 sys_stv
2020-06-22 21:55 sys_stv
2020-06-16 21:55 sys_stv
2020-05-19 21:57 sys_stv
2020-05-09  3:02 sys_stv
2020-05-08  2:08 sys_stv
2020-05-07  3:30 sys_stv
2020-04-25 23:55 sys_stv
2020-04-25  3:30 sys_stv
2020-03-17  4:42 sys_stv
2020-03-17  2:17 sys_stv
2020-01-19 21:34 sys_stv
2019-12-18  2:16 sys_stv
2019-12-16 21:25 sys_stv
2019-12-15 21:25 sys_stv
2019-12-14 21:24 sys_stv
2019-12-13 21:24 sys_stv
2019-12-12 21:24 sys_stv
2019-12-12  2:31 sys_stv
2019-11-25  2:11 sys_stv
2019-11-21 21:59 sys_stv
2019-11-21  2:29 sys_stv
2019-11-13  2:31 sys_stv
2019-11-08  6:41 sys_stv
2019-10-30 21:27 sys_stv
2019-10-29 21:29 sys_stv
2019-10-28 21:30 sys_stv
2019-10-28  2:47 sys_stv
2019-09-12 21:26 sys_stv
2019-08-22 21:24 sys_stv
2019-08-21 21:46 sys_stv
2019-08-20 21:23 sys_stv
2019-08-19 21:24 sys_stv
2019-08-07  1:20 sys_stv
2019-07-22  5:57 sys_stv
2019-07-12  1:40 sys_stv
2019-07-11  1:12 sys_stv
2019-07-09 21:32 sys_stv
2019-07-09  1:59 sys_stv
2019-07-08 10:20 sys_stv
2019-07-08  6:34 sys_stv
2019-07-04 21:50 sys_stv
2019-07-03 21:32 sys_stv
2019-07-03  5:33 sys_stv
2019-07-03  2:35 sys_stv
2019-06-28 21:31 sys_stv
2019-06-26 21:31 sys_stv
2019-06-25 21:31 sys_stv
2019-06-24 21:30 sys_stv
2019-06-23 21:31 sys_stv
2019-06-22 23:54 sys_stv
2019-06-21 21:31 sys_stv
2019-06-21  6:20 sys_stv
2019-06-20 21:31 sys_stv
2019-06-19 21:31 sys_stv
2019-06-19  1:18 sys_stv
2019-06-18 21:31 sys_stv
2019-06-14  1:23 sys_stv
2019-06-03 21:29 sys_stv
2019-06-02 21:29 sys_stv
2019-06-01 21:28 sys_stv
2019-05-31 21:30 sys_stv
2019-05-31  3:16 sys_stv
2019-05-29 21:29 sys_stv
2019-05-28 21:28 sys_stv
2019-05-16 21:26 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='ee68f5$740hsh@orsmga001.jf.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).