Re: [dpdk-test-report] |FAILURE|dpdk-master daily Intel builds (5/17)

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

From: Thomas Monjalon <thomas@monjalon.net>
To: sys_stv@intel.com
Cc: test-report@dpdk.org, dpdk_sw_eng@intel.com,
	npg.sw.core.tools.prc@intel.com, ferruh.yigit@intel.com,
	qian.q.xu@intel.com
Subject: Re: [dpdk-test-report] |FAILURE|dpdk-master daily Intel builds (5/17)
Date: Sun, 21 Apr 2019 01:25:18 +0200	[thread overview]
Message-ID: <5354906.88ojZWdado@xps> (raw)
In-Reply-To: <e75792$6mq73k@orsmga001.jf.intel.com>

Hi,
What are thebuild failures?
The logs are missing.

20/04/2019 23:10, sys_stv@intel.com:
> 
> commit 7dccd4e02bcf6eff6480e6ddc8d066b38b3ffc89
> Author: Herakliusz Lipiec <herakliusz.lipiec@intel.com>
> Date:   Fri Apr 19 11:28:52 2019 +0100
> 
>     net/tap: fix multi process reply buffer
> 
> Git Repo  :dpdk-master
> 
> Build Summary      : 17 Builds Done, 5 Successful, 12 Failures.
> 
> 
> FAILURE #1
> 
> 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,
> 
> 
> 
> FAILURE #2
> 
> 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,
> 
> 
> 
> FAILURE #3
> 
> 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,
> 
> 
> 
> FAILURE #4
> 
> 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,
> 
> 
> 
> FAILURE #5
> 
> 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,
> 
> 
> 
> FAILURE #6
> 
> 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,
> 
> 
> 
> FAILURE #7
> 
> 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,
> 
> 
> 
> FAILURE #8
> 
> 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,
> 
> 
> 
> FAILURE #9
> 
> 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,
> 
> 
> 
> FAILURE #10
> 
> 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,
> 
> 
> 
> FAILURE #11
> 
> 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,
> 
> 
> 
> FAILURE #12
> 
> 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,
> 
> 
> 
> SUCCESS #1
> 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 #2
> UBT1804/Linux 4.15.0/Clang6.0.0
> Config: x86_64-native-linuxapp-clang
> 
> SUCCESS #3
> FreeBSD12.0/Linux 19.02/Clang6.0.1
> Config: x86_64-native-bsdapp-clang
>      CONFIG_RTE_BUILD_SHARED_LIB=y
> 
> SUCCESS #4
> FreeBSD12.0/Linux 19.02/GCC7.3.0
> Config: x86_64-native-bsdapp-gcc
>      CONFIG_RTE_BUILD_SHARED_LIB=y
> 
> SUCCESS #5
> FC29/Linux 4.20/Clang6.0.1
> Config: x86_64-native-linuxapp-clang
> 
> 
> 
> DPDK STV team
>

next prev parent reply	other threads:[~2019-04-29 10:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-20 21:10 sys_stv
2019-04-20 23:25 ` Thomas Monjalon [this message]
2019-04-21 21:11 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=5354906.88ojZWdado@xps \
    --to=thomas@monjalon.net \
    --cc=dpdk_sw_eng@intel.com \
    --cc=ferruh.yigit@intel.com \
    --cc=npg.sw.core.tools.prc@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=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).