automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report]  |SUCCESS| pw53410[v2, 2/5] bbdev: extension of BBDEV for 5G FEC
Date: 15 May 2019 09:21:53 -0700	[thread overview]
Message-ID: <ee68f5$6u5dgt@orsmga001.jf.intel.com> (raw)

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

Test-Label: Intel-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/53410

_Compilation OK_

Submitter: Nicolas Chautru <nicolas.chautru@intel.com>
Date: 2019-05-14 19:45:40
Reply_mail: 1557863143-174842-3-git-send-email-nicolas.chautru@intel.com
DPDK git baseline: Repo:dpdk-next-crypto, CommitID: 93fa422f742ad9c4679a25d4b0e875856fd6a393

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

Build Summary: 17 Builds Done, 17 Successful, 0 Failures



Test environment and configuration as below:

**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)
	x86_64-native-linuxapp-gcc


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-gcc


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)
	i686-native-linuxapp-gcc


OS: SUSE12-64
	Kernel Version: 4.4.73-5-default
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (SUSE Linux) 7.1.1 20170607 [gcc-7-branch revision 248970]
	Clang Version: 3.8.0 (tags/RELEASE_380/final 262553)
	x86_64-native-linuxapp-gcc


OS: FC29-64
	Kernel Version: 4.20.13-200.fc29.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 8.3.1 20190223 (Red Hat 8.3.1-2)
	Clang Version: 7.0.1 (Fedora 7.0.1-4.fc29)
	x86_64-native-linuxapp-gcc


OS: WIN10-64
	Kernel Version: N/A
	CPU info: N/A
	GCC Version: N/A
	Clang Version: Clang 8.0.0
	x86_64-native-linuxapp-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)
	x86_64-native-bsdapp-gcc


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

**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


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-27ubuntu1~18.04) 7.3.0
	Clang Version: 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
	x86_64-native-linuxapp-icc
	x86_64-native-linuxapp-clang
	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.13.0-36-generic
	CPU info: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
	GCC Version: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609
	Clang Version: NA
	x86_64-native-linuxapp-gcc


OS: CENTOS75-64
	Kernel Version: 3.10.0-957.5.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


OS: FC29-64
	Kernel Version: 4.20.13-200.fc29.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 8.3.1 20190223 (Red Hat 8.3.1-2)
	Clang Version: 7.0.1 (Fedora 7.0.1-4.fc29)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-icc


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: UB1810-64
	Kernel Version: 4.18.0-10-generic
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (Ubuntu 8.2.0-7ubuntu1) 8.2.0
	Clang Version: 7.0.0-3 (tags/RELEASE_700/final)
	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-clang
	x86_64-native-bsdapp-gcc


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


OS: SUSE12-64
	Kernel Version: 4.4.73-5-default
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (SUSE Linux) 7.1.1 20170607 [gcc-7-branch revision 248970]
	Clang Version: 3.8.0 (tags/RELEASE_380/final 262553)
	x86_64-native-linuxapp-gcc

*Meson Failed Build #1:
OS: WIN10-64
Target: x86_64-native-linuxapp-clang
Program sphinx-build found: NO
Library execinfo found: NO

examples\meson.build:11:0: ERROR: Program or command 'sh' not found or not executable

A full log can be found at C:\win-dpdk\dpdk\build\meson-logs\meson-log.txt
ninja: Entering directory `build'

*Meson Failed Build #2:
OS: CENTOS76-64
Target: x86_64-native-linuxapp-gcc
../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
[1070/1660] Compiling C object 'drivers/a715181@@tmp_rte_pmd_caam_jr@sta/crypto_caam_jr_caam_jr_capabilities.c.o'.
[1071/1660] Compiling C object 'drivers/a715181@@rte_pmd_aesni_gcm@sta/meson-generated_.._rte_pmd_aesni_gcm.pmd.c.o'.
[1072/1660] Compiling C object 'drivers/a715181@@tmp_rte_pmd_vmxnet3@sta/net_vmxnet3_vmxnet3_rxtx.c.o'.
[1073/1660] Compiling C object 'drivers/a715181@@tmp_rte_pmd_caam_jr@sta/crypto_caam_jr_caam_jr_hw.c.o'.
[1074/1660] Compiling C object 'drivers/a715181@@tmp_rte_pmd_virtio@sta/net_virtio_virtio_rxtx.c.o'.
ninja: build stopped: subcommand failed.
meson --werror -Dexamples=all --default-library=shared /tmp/CENTOS76-64_K3.10.0_GCC4.8.5/x86_64-native-linuxapp-gcc/c57c5270b21b40f5acf71d09acb62c1b/dpdk/devtools/.. build-gcc-shared
The Meson build system
Version: 0.50.0
--
../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
[1085/1680] Compiling C object 'drivers/a715181@@tmp_rte_pmd_aesni_gcm@sta/crypto_aesni_gcm_aesni_gcm_pmd.c.o'.
[1086/1680] Compiling C object 'drivers/a715181@@tmp_rte_pmd_vmxnet3@sta/net_vmxnet3_vmxnet3_ethdev.c.o'.
[1087/1680] Compiling C object 'drivers/a715181@@tmp_rte_pmd_aesni_mb@sta/crypto_aesni_mb_rte_aesni_mb_pmd_ops.c.o'.
[1088/1680] Compiling C object 'drivers/a715181@@tmp_rte_pmd_vmxnet3@sta/net_vmxnet3_vmxnet3_rxtx.c.o'.
[1089/1680] Compiling C object 'drivers/a715181@@tmp_rte_pmd_virtio@sta/net_virtio_virtio_rxtx.c.o'.
ninja: build stopped: subcommand failed.
meson --werror -Dexamples=all --default-library=static /tmp/CENTOS76-64_K3.10.0_GCC4.8.5/x86_64-native-linuxapp-gcc/c57c5270b21b40f5acf71d09acb62c1b/dpdk/devtools/.. build-clang-static
The Meson build system
Version: 0.50.0
--
Compiler for C supports arguments -Wno-address-of-packed-member: NO
Fetching value of define "__SSE4_2__" : 

config/x86/meson.build:22:1: ERROR: Problem encountered: SSE4.2 instruction set is required for DPDK.
Please set the machine type to "nehalem" or "corei7" or higher value

A full log can be found at /tmp/CENTOS76-64_K3.10.0_GCC4.8.5/x86_64-native-linuxapp-gcc/c57c5270b21b40f5acf71d09acb62c1b/dpdk/build-clang-static/meson-logs/meson-log.txt
--
Compiler for C supports arguments -Wno-address-of-packed-member: NO
Fetching value of define "__SSE4_2__" : 

config/x86/meson.build:22:1: ERROR: Problem encountered: SSE4.2 instruction set is required for DPDK.
Please set the machine type to "nehalem" or "corei7" or higher value

A full log can be found at /tmp/CENTOS76-64_K3.10.0_GCC4.8.5/x86_64-native-linuxapp-gcc/c57c5270b21b40f5acf71d09acb62c1b/dpdk/build-clang-shared/meson-logs/meson-log.txt
--
../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
[1090/1684] Compiling C object 'drivers/a715181@@tmp_rte_pmd_caam_jr@sta/crypto_caam_jr_caam_jr_capabilities.c.o'.
[1091/1684] Compiling C object 'drivers/a715181@@tmp_rte_pmd_vmxnet3@sta/net_vmxnet3_vmxnet3_ethdev.c.o'.
[1092/1684] Compiling C object 'drivers/a715181@@tmp_rte_pmd_aesni_gcm@sta/crypto_aesni_gcm_aesni_gcm_pmd.c.o'.
[1093/1684] Compiling C object 'drivers/a715181@@tmp_rte_pmd_vmxnet3@sta/net_vmxnet3_vmxnet3_rxtx.c.o'.
[1094/1684] Compiling C object 'drivers/a715181@@tmp_rte_pmd_virtio@sta/net_virtio_virtio_rxtx.c.o'.
ninja: build stopped: subcommand failed.

DPDK STV team

                 reply	other threads:[~2019-05-15 16:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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$6u5dgt@orsmga001.jf.intel.com' \
    --to=sys_stv@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).