[dpdk-test-report] | FAILURE daily Intel builds (19/20)

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 (19/20)
Date: 03 Mar 2019 19:42:00 -0800	[thread overview]
Message-ID: <e75792$4kh25j@orsmga001.jf.intel.com> (raw)

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


commit 902f389f9b4cad1feba320e8b779432eeb76cada
Author: Andrius Sirvys <andrius.sirvys@intel.com>
Date:   Tue Feb 19 13:24:50 2019 +0000

    drivers/net: fix shifting 32-bit signed variable 31 times


Build Summary      : 20 Builds Done, 19 Successful, 1 Failures.


FAILURE #1

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

  CC ifpga_fme.o
  CC ifpga_fme_iperf.o
  AR librte_pmd_skeleton_rawdev.a
  INSTALL-LIB librte_pmd_skeleton_rawdev.a
  CC ifpga_fme_dperf.o
  CC ifpga_fme_error.o
  CC ifpga_port.o
  CC ifpga_port_error.o
  CC opae_hw_api.o
  CC opae_ifpga_hw_api.o
  CC opae_debug.o
  CC ifpga_fme_pr.o
  CC ifpga_rawdev.o
--
  INSTALL-APP vmdq_dcb_app
  INSTALL-MAP vmdq_dcb_app.map
  LD eventdev_pipeline
  INSTALL-APP eventdev_pipeline
  INSTALL-MAP eventdev_pipeline.map
cp: error writing '/tmp/FC28_K4.16.3_Clang6.0.1/x86_64-native-linuxapp-clang/aeae411a45ea445fa49599e21cad793a/dpdk/examples/eventdev_pipeline/x86_64-native-linuxapp-clang/app/eventdev_pipeline.map': No space left on device
make[4]: *** [/tmp/FC28_K4.16.3_Clang6.0.1/x86_64-native-linuxapp-clang/aeae411a45ea445fa49599e21cad793a/dpdk/mk/rte.app.mk:425: /tmp/FC28_K4.16.3_Clang6.0.1/x86_64-native-linuxapp-clang/aeae411a45ea445fa49599e21cad793a/dpdk/examples/eventdev_pipeline/x86_64-native-linuxapp-clang/app/eventdev_pipeline.map] Error 1
make[3]: *** [/tmp/FC28_K4.16.3_Clang6.0.1/x86_64-native-linuxapp-clang/aeae411a45ea445fa49599e21cad793a/dpdk/mk/rte.extapp.mk:15: all] Error 2
make[2]: *** [/tmp/FC28_K4.16.3_Clang6.0.1/x86_64-native-linuxapp-clang/aeae411a45ea445fa49599e21cad793a/dpdk/mk/rte.extsubdir.mk:21: eventdev_pipeline] Error 2
make[1]: *** [/tmp/FC28_K4.16.3_Clang6.0.1/x86_64-native-linuxapp-clang/aeae411a45ea445fa49599e21cad793a/dpdk/mk/rte.sdkexamples.mk:26: x86_64-native-linuxapp-clang_examples] Error 2
make: *** [/tmp/FC28_K4.16.3_Clang6.0.1/x86_64-native-linuxapp-clang/aeae411a45ea445fa49599e21cad793a/dpdk/mk/rte.sdkroot.mk:94: examples] Error 2

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-32/Linux 4.4.0/GCC5.4.0
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 #3

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

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

SUCCESS #5

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 #6

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

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 #9

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 #10

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

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

SUCCESS #13

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

SUCCESS #14

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

SUCCESS #15

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

SUCCESS #16

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 #17

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 #18

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 #19

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,



DPDK STV team

next             reply	other threads:[~2019-03-04  3:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04  3:42 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-24 20:22 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='e75792$4kh25j@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).