[dpdk-dev] FW: [dpdk-test-report] | ERROR | daily Intel builds (37/43)

DPDK patches and discussions
 help / color / mirror / Atom feed

From: "Wei, FangfangX" <fangfangx.wei@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] FW: [dpdk-test-report] | ERROR | daily Intel builds (37/43)
Date: Wed, 15 Mar 2017 08:06:44 +0000	[thread overview]
Message-ID: <067B569323FEB248B5CB480E1954F4346EA0FC92@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <63cbe6$121995t@fmsmga002.fm.intel.com>

Hi all,
There's one build error which was brought by commit "0fe9830b53452a6747cae9ff1a6bfc737b839a9d".

commit 0fe9830b53452a6747cae9ff1a6bfc737b839a9d
Author: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
Date:   Mon Mar 6 20:34:15 2017 +0530

    eal/ppc: support sPAPR IOMMU for vfio-pci

    Below changes adds pci probing support for vfio-pci devices in power8.

    Signed-off-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
    Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
    Acked-by: Chao Zhu <chaozhu@linux.vnet.ibm.com>


Best Regards
Fangfang Wei


-----Original Message-----
From: test-report [mailto:test-report-bounces@dpdk.org] On Behalf Of sys_stv@intel.com
Sent: Wednesday, March 15, 2017 4:14 AM
To: test-report@dpdk.org
Subject: [dpdk-test-report] | ERROR | daily Intel builds (37/43)

Last commit Time   : Fri Mar 10 15:38:47 2017 +0100
Last Author        : Keith Wiles
Last commit Hash   : 9d5ca5323910591f2cafbac5070fcb5b6d02d022
Last comment       : examples: fix optind reset

Build Summary      : 43 Builds Done, 37 Successful, 6 Failures.

Failure details    : 

Failure #1
SUSE12SP3_64 / Linux 3.7.10-1 / GCC 4.7.2
Config: x86_64-native-linuxapp-gcc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

/homeDPDK/lib/librte_eal/linuxapp/eal/eal_vfio.c: In function ‘vfio_spapr_dma_map’:
/homeDPDK/lib/librte_eal/linuxapp/eal/eal_vfio.c:555:9: error: variable ‘info’ has initializer but incomplete type compilation terminated due to -Wfatal-errors.

Failure #2
SUSE12SP3_64 / Linux 3.7.10-1 / ICC 16.0.2
Config: x86_64-native-linuxapp-icc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

/homeDPDK/lib/librte_eal/linuxapp/eal/eal_vfio.c: In function ‘vfio_spapr_dma_map’:
/homeDPDK/lib/librte_eal/linuxapp/eal/eal_vfio.c:555:9: error: variable ‘info’ has initializer but incomplete type compilation terminated due to -Wfatal-errors.

Failure #3
RHEL70_64 / Linux 3.10.0-123 / GCC 4.8.5
Config: x86_64-native-linuxapp-gcc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

DPDK/lib/librte_eal/linuxapp/eal/eal_vfio.c: In function ‘vfio_spapr_dma_map’:
DPDK/lib/librte_eal/linuxapp/eal/eal_vfio.c:555:9: error: variable ‘info’ has initializer but incomplete type
  struct vfio_iommu_spapr_tce_info info = {
         ^
compilation terminated due to -Wfatal-errors.

Failure #4
RHEL70_64 / Linux 3.10.0-123 / ICC 14.0.0
Config: x86_64-native-linuxapp-icc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

DPDK/lib/librte_eal/linuxapp/eal/eal_vfio.c: In function ‘vfio_spapr_dma_map’:
DPDK/lib/librte_eal/linuxapp/eal/eal_vfio.c:555:9: error: variable ‘info’ has initializer but incomplete type
  struct vfio_iommu_spapr_tce_info info = {
         ^
compilation terminated due to -Wfatal-errors.

Failure #5
FC18_64 / Linux 3.6.10-4 / GCC 4.7.2
Config: x86_64-native-linuxapp-gcc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

DPDK/lib/librte_eal/linuxapp/eal/eal_vfio.c: In function ‘vfio_spapr_dma_map’:
DPDK/lib/librte_eal/linuxapp/eal/eal_vfio.c:555:9: error: variable ‘info’ has initializer but incomplete type compilation terminated due to -Wfatal-errors.

Failure #6
FC18_64 / Linux 3.6.10-4 / ICC 14.0.0
Config: x86_64-native-linuxapp-icc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

DPDK/lib/librte_eal/linuxapp/eal/eal_vfio.c: In function ‘vfio_spapr_dma_map’:
DPDK/lib/librte_eal/linuxapp/eal/eal_vfio.c:555:9: error: variable ‘info’ has initializer but incomplete type compilation terminated due to -Wfatal-errors.

Successful builds :
SUSE12SP3_64 / Linux 3.7.10-1 / CLANG 3.2
Config: x86_64-native-linuxapp-clang

FreeBSD10.0_64 / Linux 10.0-RELEASE / GCC 4.8.4
Config: x86_64-native-bsdapp-gcc
        CONFIG_RTE_BUILD_SHARED_LIB=y

FreeBSD10.0_64 / Linux 10.0-RELEASE / CLANG 3.3
Config: x86_64-native-bsdapp-clang
        CONFIG_RTE_BUILD_SHARED_LIB=y

FC20_64 / Linux 3.15.6-200 / GCC 4.8.3
Config: x86_64-native-linuxapp-gcc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

FC20_64 / Linux 3.15.6-200 / ICC 14.0.0
Config: x86_64-native-linuxapp-icc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

FC20_64 / Linux 3.15.6-200 / CLANG 3.4
Config: x86_64-native-linuxapp-clang

FreeBSD10.3_64 / Linux 10.3-RELEASE / GCC 4.8.5
Config: x86_64-native-bsdapp-gcc
        CONFIG_RTE_BUILD_SHARED_LIB=y

FreeBSD10.3_64 / Linux 10.3-RELEASE / CLANG 3.4.1
Config: x86_64-native-bsdapp-clang
        CONFIG_RTE_BUILD_SHARED_LIB=y

RHEL72_64 / Linux 3.10.0-327 / GCC 4.8.5
Config: x86_64-native-linuxapp-gcc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

RHEL72_64 / Linux 3.10.0-327 / ICC 16.0.2
Config: x86_64-native-linuxapp-icc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

RHEL72_64 / Linux 3.10.0-327 / CLANG 3.4.2
Config: x86_64-native-linuxapp-clang

UBT124_64 / Linux 3.8.0-29 / GCC 4.6.3
Config: x86_64-native-linuxapp-gcc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

UBT124_64 / Linux 3.8.0-29 / ICC 14.0.0
Config: x86_64-native-linuxapp-icc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

UBT124_64 / Linux 3.8.0-29 / CLANG 3.0-6ubuntu3
Config: x86_64-native-linuxapp-clang

FC20_32 / Linux 3.19.8-100 / GCC 4.8.3
Config: i686-native-linuxapp-gcc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y

FC20_32 / Linux 3.19.8-100 / ICC 15.0.0
Config: i686-native-linuxapp-icc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y

RHEL70_64 / Linux 3.10.0-123 / CLANG 3.4.2
Config: x86_64-native-linuxapp-clang

UBT144_64 / Linux 3.13.0-30 / GCC 4.8.2
Config: x86_64-native-linuxapp-gcc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

UBT144_64 / Linux 3.13.0-30 / ICC 14.0.0
Config: x86_64-native-linuxapp-icc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

UBT144_64 / Linux 3.13.0-30 / CLANG 3.4-1ubuntu3
Config: x86_64-native-linuxapp-clang

FC21_64 / Linux 4.1.13-100 / GCC 4.9.2
Config: x86_64-native-linuxapp-gcc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

FC21_64 / Linux 4.1.13-100 / ICC 16.0.2
Config: x86_64-native-linuxapp-icc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

FC21_64 / Linux 4.1.13-100 / CLANG 3.5.0
Config: x86_64-native-linuxapp-clang

UBT144_32 / Linux 3.13.0-30 / GCC 4.8.4
Config: i686-native-linuxapp-gcc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y

UBT144_32 / Linux 3.13.0-30 / ICC 16.0.2
Config: i686-native-linuxapp-icc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y

CENTOS70_64 / Linux 3.10.0-327 / GCC 4.8.5
Config: x86_64-native-linuxapp-gcc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

CENTOS70_64 / Linux 3.10.0-327 / ICC 16.0.2
Config: x86_64-native-linuxapp-icc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

CENTOS70_64 / Linux 3.10.0-327 / CLANG 3.4.2
Config: x86_64-native-linuxapp-clang

UBT164_64 / Linux 4.4.0-53 / GCC 5.4.0
Config: x86_64-native-linuxapp-gcc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

UBT164_64 / Linux 4.4.0-53 / ICC 16.0.2
Config: x86_64-native-linuxapp-icc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

UBT164_64 / Linux 4.4.0-53 / CLANG 3.8.0-2ubuntu4
Config: x86_64-native-linuxapp-clang

FC24_64 / Linux 4.7.2-201 / GCC 6.3.1
Config: x86_64-native-linuxapp-gcc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

FC24_64 / Linux 4.7.2-201 / ICC 16.0.2
Config: x86_64-native-linuxapp-icc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

FC24_64 / Linux 4.7.2-201 / CLANG 3.8.0
Config: x86_64-native-linuxapp-clang

FC18_64 / Linux 3.6.10-4 / CLANG 3.1
Config: x86_64-native-linuxapp-clang

SUSE11SP2_64 / Linux 3.0.13-0 / GCC 4.5.1
Config: x86_64-native-linuxapp-gcc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

SUSE11SP2_64 / Linux 3.0.13-0 / ICC 14.0.0
Config: x86_64-native-linuxapp-icc
        CONFIG_RTE_LIBRTE_PMD_PCAP=y,
        CONFIG_RTE_NIC_BYPASS=y,
        CONFIG_RTE_BUILD_SHARED_LIB=y,
        CONFIG_RTE_LIBRTE_VHOST=y,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

next      parent reply	other threads:[~2017-03-15  8:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <63cbe6$121995t@fmsmga002.fm.intel.com>
2017-03-15  8:06 ` Wei, FangfangX [this message]
2017-03-15  8:58   ` Burakov, Anatoly

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=067B569323FEB248B5CB480E1954F4346EA0FC92@SHSMSX101.ccr.corp.intel.com \
    --to=fangfangx.wei@intel.com \
    --cc=dev@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).