[dpdk-test-report] | ERROR | daily Intel builds (26/33)

automatic DPDK test reports
 help / color / mirror / Atom feed

From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] | ERROR | daily Intel builds (26/33)
Date: 14 Jul 2016 15:29:47 -0700	[thread overview]
Message-ID: <39c2d4$p7ae2u@orsmga003.jf.intel.com> (raw)

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

Last commit Time   : Mon Jul 11 21:47:34 2016 +0200
Last Author        : Thomas Monjalon
Last commit Hash   : 11c5e45d88ff3fcb86be4a1c23c766b35bafdc70
Last comment       : version: 16.07-rc2

Build Summary      : 33 Builds Done, 26 Successful, 7 Failures.

Failure details    : 

Failure #1
UBT144_32 / Linux 3.13.0-30 / ICC 14.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

PMDINFO ena_ethdev.o.pmd.c  LD ena_ethdev.oDPDK/drivers/net/ena/base/ena_com.c(346): error #3656: variable "dev_node" may be used before its value is set
  		ENA_MEM_ALLOC_COHERENT_NODE(ena_dev->dmadev,
  		^
compilation aborted for DPDK/drivers/net/ena/base/ena_com.c (code 4)

Failure #2
UBT124_64 / Linux 3.8.0-29 / GCC 4.6.3
Config: x86_64-native-ivshmem-gcc

MKRES test_resource_c.res.o  DPDK/x86_64-ivshmem-linuxapp-gcc/lib/librte_eal.a(eal_alarm.o): In function `eal_alarm_callback':
eal_alarm.c:(.text+0xda): undefined reference to `clock_gettime'
DPDK/x86_64-ivshmem-linuxapp-gcc/lib/librte_eal.a(eal_alarm.o): In function `rte_eal_alarm_set':
eal_alarm.c:(.text+0x211): undefined reference to `clock_gettime'
DPDK/x86_64-ivshmem-linuxapp-gcc/lib/librte_eal.a(eal_timer.o): In function `get_tsc_freq':
eal_timer.c:(.text+0x128): undefined reference to `clock_gettime'
eal_timer.c:(.text+0x166): undefined reference to `clock_gettime'
collect2: ld returned 1 exit status

Failure #3
FC18_64 / Linux 3.6.10-4 / GCC 4.7.2
Config: x86_64-native-ivshmem-gcc

MKRES test_resource_c.res.o  DPDK/x86_64-ivshmem-linuxapp-gcc/lib/librte_eal.a(eal_alarm.o): In function `eal_alarm_callback':
eal_alarm.c:(.text+0xd7): undefined reference to `clock_gettime'
DPDK/x86_64-ivshmem-linuxapp-gcc/lib/librte_eal.a(eal_alarm.o): In function `rte_eal_alarm_set':
eal_alarm.c:(.text+0x20f): undefined reference to `clock_gettime'
DPDK/x86_64-ivshmem-linuxapp-gcc/lib/librte_eal.a(eal_timer.o): In function `get_tsc_freq':
eal_timer.c:(.text+0x108): undefined reference to `clock_gettime'
eal_timer.c:(.text+0x146): undefined reference to `clock_gettime'
collect2: error: ld returned 1 exit status

Failure #4
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

DPDK/examples/ipsec-secgw/sa.c:56:2: error: unknown field ‘ip4’ specified in initializer
compilation terminated due to -Wfatal-errors.

Failure #5
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

DPDK/examples/ipsec-secgw/sa.c:56:2: error: unknown field ‘ip4’ specified in initializer
compilation terminated due to -Wfatal-errors.

Failure #6
SUSE11SP2_64 / Linux 3.0.13-0 / GCC 4.5.1
Config: x86_64-native-ivshmem-gcc

MKRES test_resource_c.res.o  DPDK/x86_64-ivshmem-linuxapp-gcc/lib/librte_eal.a(eal_alarm.o): In function `eal_alarm_callback':
eal_alarm.c:(.text+0xd8): undefined reference to `clock_gettime'
DPDK/x86_64-ivshmem-linuxapp-gcc/lib/librte_eal.a(eal_alarm.o): In function `rte_eal_alarm_set':
eal_alarm.c:(.text+0x262): undefined reference to `clock_gettime'
collect2: ld returned 1 exit status

Failure #7
SUSE11SP2_64 / Linux 3.0.13-0 / ICC 14.0.0
Config: x86_64-native-ivshmem-icc

MKRES test_resource_c.res.o  DPDK/x86_64-ivshmem-linuxapp-gcc/lib/librte_eal.a(eal_alarm.o): In function `eal_alarm_callback':
eal_alarm.c:(.text+0xd8): undefined reference to `clock_gettime'
DPDK/x86_64-ivshmem-linuxapp-gcc/lib/librte_eal.a(eal_alarm.o): In function `rte_eal_alarm_set':
eal_alarm.c:(.text+0x262): undefined reference to `clock_gettime'
collect2: ld returned 1 exit status

Successful builds :
UBT144_32 / Linux 3.13.0-30 / GCC 4.8.2
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_64 / Linux 3.15.6-200 / GCC 4.8.2
Config: x86_64-native-ivshmem-gcc

FC20_64 / Linux 3.15.6-200 / ICC 14.0.0
Config: x86_64-native-ivshmem-icc

FC20_64 / Linux 3.15.6-200 / GCC 4.8.2
Config: x86_64-native-linuxapp-gcc
        enable_all_DEBUG_OPTION=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

FC20_64 / Linux 3.15.6-200 / CLANG 3.4
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

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

UBT144_64 / Linux 3.13.0-30 / GCC 4.8.2
Config: x86_64-native-ivshmem-gcc

UBT144_64 / Linux 3.13.0-30 / ICC 14.0.0
Config: x86_64-native-ivshmem-icc

FC20_32 / Linux 3.11.0 / 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.11.0 / ICC 14.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 / 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

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

RHEL70_64 / Linux 3.10.0-123 / GCC 4.8.2
Config: x86_64-native-ivshmem-gcc

RHEL70_64 / Linux 3.10.0-123 / ICC 14.0.0
Config: x86_64-native-ivshmem-icc

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

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

UBT124_64 / Linux 3.8.0-29 / ICC 14.0.0
Config: x86_64-native-ivshmem-icc

FC21_64 / Linux 3.18.8-201 / GCC 4.9.2
Config: x86_64-native-ivshmem-gcc

FC21_64 / Linux 3.18.8-201 / ICC 15.0.0
Config: x86_64-native-ivshmem-icc

FC21_64 / Linux 3.18.8-201 / 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

FC21_64 / Linux 3.18.8-201 / ICC 15.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

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

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

FC18_64 / Linux 3.6.10-4 / ICC 14.0.0
Config: x86_64-native-ivshmem-icc

next             reply	other threads:[~2016-07-14 22:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14 22:29 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-07-14  7:50 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='39c2d4$p7ae2u@orsmga003.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).