automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw57604crypto/qat: fix null auth issues when using vfio_pci
Date: 09 Aug 2019 02:57:58 -0700	[thread overview]
Message-ID: <ee68f5$7mvusb@orsmga001.jf.intel.com> (raw)

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

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/57604

_Compilation issues_

Submitter: Damian Nowak <damianx.nowak@intel.com>
Date: 2019-08-09 09:29:01
Reply_mail: 20190809092901.17788-1-damianx.nowak@intel.com
DPDK git baseline: Repo:dpdk-next-crypto, CommitID: 0710d87b7f5d0a2cd01861d44c4689efd4714b5f

Makefile build Summary: 22 Builds Done, 21 Successful, 1 Failures

Meson build Summary: 8 Builds Done, 7 Successful, 1 Failures

               +==============================================+===========+==========+
               |                   Makefile                   |   Meson   | Document |
+--------------+------+-------+------+------------+-----------+-----------+----------+
| os           | gcc  | clang | icc  | gcc+shared | gcc+debug | gcc/clang | pdf/html |
+--------------+------+-------+------+------------+-----------+-----------+----------+
| RHEL76-64    | pass |       |      |            |           |           |          |
| CENTOS76-64  | pass |       |      |            |           |           |          |
| UB1804-64    | pass | pass  | pass |            |           | pass      | pass     |
| UB1604-32    | pass |       |      |            |           | pass      |          |
| UB1904-64    | pass |       |      |            |           |           |          |
| UB1604-64    | pass | pass  |      |            |           |           |          |
| FC30-64      | FAIL | pass  |      |            |           | FAIL      |          |
| WIN10-64     |      |       |      |            |           | pass      |          |
| FreeBSD12-64 | pass | pass  |      | pass       | pass      | pass      |          |
| RHEL80-64    | pass | pass  | pass | pass       | pass      | pass      |          |
| SUSE15-64    | pass | pass  |      |            |           | pass      |          |
+--------------+------+-------+------+------------+-----------+-----------+----------+

Test environment and configuration as below:

** Makefile 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: 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: FC30-64
	Kernel Version: 5.1.7-300.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


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-clang
	x86_64-native-bsdapp-gcc+debug
	x86_64-native-bsdapp-gcc+shared
	x86_64-native-bsdapp-gcc


OS: RHEL80-64
	Kernel Version: 4.18.0-80.el8.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 8.2.1 20180905 (Red Hat 8.2.1-3)
	Clang Version: NA
	x86_64-native-linuxapp-gcc+debug
	x86_64-native-linuxapp-gcc+shared
	x86_64-native-linuxapp-icc
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-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
	x86_64-native-linuxapp-clang


** Meson build **


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: FC30-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


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.99-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: RHEL80-64
	Kernel Version: 4.18.0-80.el8.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
	GCC Version: gcc (GCC) 8.2.1 20180905 (Red Hat 8.2.1-3)
	Clang Version: NA
	build-gcc-static
	build-gcc-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


*Make Build Failed #1:
OS: FC30-64
Target: x86_64-native-linuxapp-gcc
/tmp/FC30-64_K4.20_GCC9.1.1/x86_64-native-linuxapp-gcc/57ba9b198fc644a592f3eeb8e2f1f1be/dpdk/drivers/net/memif/memif_socket.c: In function ‘memif_socket_init’:
/tmp/FC30-64_K4.20_GCC9.1.1/x86_64-native-linuxapp-gcc/57ba9b198fc644a592f3eeb8e2f1f1be/dpdk/drivers/net/memif/memif_socket.c:1114:17: note: format string is defined here
 1114 |   MIF_LOG(ERR, "%s: Failed to register interrupt callback "
      |                 ^~
cc1: all warnings being treated as errors
make[6]: *** [/tmp/FC30-64_K4.20_GCC9.1.1/x86_64-native-linuxapp-gcc/57ba9b198fc644a592f3eeb8e2f1f1be/dpdk/mk/internal/rte.compile-pre.mk:116: memif_socket.o] Error 1
make[6]: *** Waiting for unfinished jobs....
  CC ice_nvm.o
  CC ixgbe_82599.o
  PMDINFO hinic_pmd_ethdev.o.pmd.c
  CC hinic_pmd_ethdev.o.pmd.o
--
  LD rte_eth_memif.o
  CC hinic_pmd_tx.o
  CC lio_rxtx.o
  CC i40e_ethdev.o
  CC iavf_rxtx_vec_sse.o
make[5]: *** [/tmp/FC30-64_K4.20_GCC9.1.1/x86_64-native-linuxapp-gcc/57ba9b198fc644a592f3eeb8e2f1f1be/dpdk/mk/rte.subdir.mk:35: memif] Error 2
make[5]: *** Waiting for unfinished jobs....
== Build drivers/net/netvsc
  CC i40e_rxtx.o
  CC ixgbe_x540.o
  CC ipn3ke_tm.o
--
  PMDINFO ixgbe_ethdev.o.pmd.c
  CC ixgbe_ethdev.o.pmd.o
  LD ixgbe_ethdev.o
  AR librte_pmd_ixgbe.a
  INSTALL-LIB librte_pmd_ixgbe.a
make[4]: *** [/tmp/FC30-64_K4.20_GCC9.1.1/x86_64-native-linuxapp-gcc/57ba9b198fc644a592f3eeb8e2f1f1be/dpdk/mk/rte.subdir.mk:35: net] Error 2
make[3]: *** [/tmp/FC30-64_K4.20_GCC9.1.1/x86_64-native-linuxapp-gcc/57ba9b198fc644a592f3eeb8e2f1f1be/dpdk/mk/rte.sdkbuild.mk:46: drivers] Error 2
make[2]: *** [/tmp/FC30-64_K4.20_GCC9.1.1/x86_64-native-linuxapp-gcc/57ba9b198fc644a592f3eeb8e2f1f1be/dpdk/mk/rte.sdkroot.mk:99: all] Error 2
make[1]: *** [/tmp/FC30-64_K4.20_GCC9.1.1/x86_64-native-linuxapp-gcc/57ba9b198fc644a592f3eeb8e2f1f1be/dpdk/mk/rte.sdkinstall.mk:61: pre_install] Error 2
make: *** [/tmp/FC30-64_K4.20_GCC9.1.1/x86_64-native-linuxapp-gcc/57ba9b198fc644a592f3eeb8e2f1f1be/dpdk/mk/rte.sdkroot.mk:77: install] Error 2

*Meson Build Failed #1:
OS: FC30-64
Target:build-gcc-static
FAILED: drivers/a715181@@tmp_rte_pmd_memif@sta/net_memif_memif_socket.c.o 
gcc -Idrivers/a715181@@tmp_rte_pmd_memif@sta -Idrivers -I../drivers -Idrivers/net/memif -I../drivers/net/memif -Ilib/librte_ethdev -I../lib/librte_ethdev -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_net -I../lib/librte_net -Ilib/librte_mbuf -I../lib/librte_mbuf -Ilib/librte_mempool -I../lib/librte_mempool -Ilib/librte_ring -I../lib/librte_ring -Ilib/librte_meter -I../lib/librte_meter -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/librte_pci -I../lib/librte_pci -Idrivers/bus/vdev -I../drivers/bus/vdev -Ilib/librte_hash -I../lib/librte_hash -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Werror -O3 -include rte_config.h -Wunused-parameter -Wsign-compare -Wcast-qual -Wno-address-of-packed-member -D_GNU_SOURCE -fPIC -march=native -mno-avx512f -Wno-format-truncation -DALLOW_EXPERIMENTAL_API -MD -MQ 'drivers/a715181@@tmp_rte_pmd_memif@sta/net_memif_memif_socket.c.o' -MF 'drivers/a715181@@tmp_rte_pmd_memif@sta/net_memif_memif_socket.c.o.d' -o 'drivers/a715181@@tmp_rte_pmd_memif@sta/net_memif_memif_socket.c.o' -c ../drivers/net/memif/memif_socket.c
In file included from ../drivers/net/memif/memif_socket.c:26:
In function ‘memif_socket_create’,
    inlined from ‘memif_socket_init’ at ../drivers/net/memif/memif_socket.c:965:12:
../drivers/net/memif/rte_eth_memif.h:35:2: error: ‘%s’ directive argument is null [-Werror=format-overflow=]
   35 |  rte_log(RTE_LOG_ ## level, memif_logtype, \
      |  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   36 |   "%s(): " fmt "\n", __func__, ##args)
      |   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/memif/memif_socket.c:920:2: note: in expansion of macro ‘MIF_LOG’
  920 |  MIF_LOG(ERR, "%s: Failed to setup socket %s: %s",
      |  ^~~~~~~
../drivers/net/memif/memif_socket.c: In function ‘memif_socket_init’:
../drivers/net/memif/memif_socket.c:1114:17: note: format string is defined here
 1114 |   MIF_LOG(ERR, "%s: Failed to register interrupt callback "
      |                 ^~
In file included from ../drivers/net/memif/memif_socket.c:26:
In function ‘memif_socket_create’,
    inlined from ‘memif_socket_init’ at ../drivers/net/memif/memif_socket.c:965:12:
../drivers/net/memif/rte_eth_memif.h:35:2: error: ‘%s’ directive argument is null [-Werror=format-overflow=]
   35 |  rte_log(RTE_LOG_ ## level, memif_logtype, \
      |  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   36 |   "%s(): " fmt "\n", __func__, ##args)
      |   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/memif/memif_socket.c:920:2: note: in expansion of macro ‘MIF_LOG’
  920 |  MIF_LOG(ERR, "%s: Failed to setup socket %s: %s",
      |  ^~~~~~~
../drivers/net/memif/memif_socket.c: In function ‘memif_socket_init’:
../drivers/net/memif/memif_socket.c:1114:17: note: format string is defined here
 1114 |   MIF_LOG(ERR, "%s: Failed to register interrupt callback "
      |                 ^~
cc1: all warnings being treated as errors
[909/1784] Compiling C object 'drivers/a715181@@tmp_rte_pmd_liquidio@sta/net_liquidio_lio_rxtx.c.o'.
[910/1784] Compiling C object 'drivers/a715181@@tmp_rte_pmd_ixgbe@sta/net_ixgbe_ixgbe_rxtx.c.o'.
[911/1784] Compiling C object 'drivers/a715181@@tmp_rte_pmd_netvsc@sta/net_netvsc_hn_nvs.c.o'.
[912/1784] Compiling C object 'drivers/a715181@@tmp_rte_pmd_netvsc@sta/net_netvsc_hn_ethdev.c.o'.
[913/1784] Compiling C object 'drivers/a715181@@tmp_rte_pmd_netvsc@sta/net_netvsc_hn_rndis.c.o'.
[914/1784] Compiling C object 'drivers/a715181@@tmp_rte_pmd_memif@sta/net_memif_rte_eth_memif.c.o'.
[915/1784] Compiling C object 'drivers/a715181@@tmp_rte_pmd_netvsc@sta/net_netvsc_hn_rxtx.c.o'.
ninja: build stopped: subcommand failed



DPDK STV team

                 reply	other threads:[~2019-08-09  9:58 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$7mvusb@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).