[dpdk-test-report] | SUCCESS | daily Intel builds (21/21)

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

From: sys_stv@intel.com
To: test-report@dpdk.org, thomas@monjalon.net
Subject: [dpdk-test-report] | SUCCESS | daily Intel builds (21/21)
Date: 19 Nov 2017 18:51:56 -0800	[thread overview]
Message-ID: <daf904$40r8e@orsmga003.jf.intel.com> (raw)

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

Last commit Time   : Wed Nov 15 19:00:28 2017 +0100
Last Author        : Thomas Monjalon
Last commit Hash   : d84aad650401a122cb75bd5811e49b03ef3dc49d
Last comment       : version: 17.11.0

Build Summary      : 21 Builds Done, 21 Successful, 0 Failures.



Successful builds :
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 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

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

FC25_64 / Linux 4.8.6-300 / 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

FC25_64 / Linux 4.8.6-300 / 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

FC25_64 / Linux 4.8.6-300 / CLANG 3.9.1
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 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

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

FreeBSD11.0_64 / Linux 11.0-RELEASE-p1 / GCC 5.4.0
Config: x86_64-native-bsdapp-gcc
        CONFIG_RTE_BUILD_SHARED_LIB=y

FreeBSD11.0_64 / Linux 11.0-RELEASE-p1 / CLANG 3.8.0
Config: x86_64-native-bsdapp-clang
        CONFIG_RTE_BUILD_SHARED_LIB=y

CENTOS72_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

CENTOS72_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

CENTOS72_64 / Linux 3.10.0-327 / CLANG 3.4.2
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

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

FC18_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

FC18_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

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

                 reply	other threads:[~2017-11-20  2:51 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='daf904$40r8e@orsmga003.jf.intel.com' \
    --to=sys_stv@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).