[dpdk-test-report] | FAILURE daily Intel builds (24/25)

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 daily Intel builds (24/25)
Date: 07 Mar 2019 17:38:46 -0800	[thread overview]
Message-ID: <e75792$53nakr@orsmga001.jf.intel.com> (raw)

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


commit 1598c729595d8d59ebb9dce190401846da16c09c
Author: David Marchand <david.marchand@redhat.com>
Date:   Wed Feb 13 21:06:59 2019 +0100

    eal: fix core list validation with disabled cores


Build Summary      : 25 Builds Done, 24 Successful, 1 Failures.


FAILURE #1

FC29/Linux 4.20/ICC19.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,

== bond
== cmdline
  CC main.o
  CC main.o
  CC main.o
/tmp/FC29_K4.20_ICC19.0.0/x86_64-native-linuxapp-icc/4c8400a690a94d579a84d7126e48d9b5/dpdk/examples/bond/main.c(61): catastrophic error: cannot open source file "rte_eth_bond.h"
  #include "rte_eth_bond.h"
                           ^

compilation aborted for /tmp/FC29_K4.20_ICC19.0.0/x86_64-native-linuxapp-icc/4c8400a690a94d579a84d7126e48d9b5/dpdk/examples/bond/main.c (code 4)
make[4]: *** [/tmp/FC29_K4.20_ICC19.0.0/x86_64-native-linuxapp-icc/4c8400a690a94d579a84d7126e48d9b5/dpdk/mk/internal/rte.compile-pre.mk:116: main.o] Error 4

SUCCESS #1

UBT144-64/Linux 4.2.0/GCC4.8.4
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,

SUCCESS #2

UBT164-64/Linux 4.4.0/GCC5.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,

SUCCESS #3

UBT1804/Linux 4.15.0/Clang6.0.0
Config: x86_64-native-linuxapp-clang

SUCCESS #4

UBT144-32/Linux 3.13.0/GCC4.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,
     CONFIG_RTE_LIBRTE_PMD_QAT=y,
   CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
   CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y,

SUCCESS #5

UBT1804/Linux 4.15.0/GCC7.3.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,

SUCCESS #6

UBT1804/Linux 4.15.0/ICC19.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,

SUCCESS #7

UBT1810/Linux 4.18.0/GCC8.2.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,

SUCCESS #8

RHEL75/Linux 3.10.0/GCC4.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,

SUCCESS #9

FC28/Linux 4.16.3/GCC8.0.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,

SUCCESS #10

FC28/Linux 4.16.3/Clang6.0.1
Config: x86_64-native-linuxapp-clang

SUCCESS #11

SUSE15/Linux 4.12.14/GCC7.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,

SUCCESS #12

FreeBSD12.0/Linux 19.02/Clang6.0.1
Config: x86_64-native-bsdapp-clang
   CONFIG_RTE_BUILD_SHARED_LIB=y

SUCCESS #13

FreeBSD11.2/Linux 11.2/Clang6.0.0
Config: x86_64-native-bsdapp-clang
   CONFIG_RTE_BUILD_SHARED_LIB=y

SUCCESS #14

FreeBSD12.0/Linux 19.02/GCC7.3.0
Config: x86_64-native-bsdapp-gcc
   CONFIG_RTE_BUILD_SHARED_LIB=y

SUCCESS #15

FreeBSD11.2/Linux 11.2/GCC6.4.0
Config: x86_64-native-bsdapp-gcc
   CONFIG_RTE_BUILD_SHARED_LIB=y

SUCCESS #16

RHEL76/Linux 3.10.0/GCC4.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,

SUCCESS #17

FC29/Linux 4.20/GCC8.0.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,

SUCCESS #18

FC29/Linux 4.20/Clang6.0.1
Config: x86_64-native-linuxapp-clang

SUCCESS #19

RHEL74/Linux 3.10.0/GCC4.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,

SUCCESS #20

CENTOS74/Linux 3.10.0/GCC4.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,

SUCCESS #21

CENTOS75/Linux 3.10.0/GCC4.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,

SUCCESS #22

FC28/Linux 4.16.3/ICC19.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,

SUCCESS #23

SUSE12/Linux 3.7.10/GCC4.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,

SUCCESS #24

CENTOS76/Linux 3.10.0/GCC4.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 STV team

                 reply	other threads:[~2019-03-08  1:38 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='e75792$53nakr@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).