automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] | SUCCESS | daily Intel builds (4/4)
Date: 04 Oct 2017 13:10:40 -0700	[thread overview]
Message-ID: <8a7c36$13432sq@orsmga001.jf.intel.com> (raw)

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

Last commit Time   : Tue Oct 3 11:28:27 2017 +0200
Last Author        : Stephen Hemminger
Last commit Hash   : f0dab530f41689651192cebd7683cddbfc9991e2
Last comment       : eal: initialize logging before bus

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



Successful builds :
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,
        CONFIG_RTE_LIBRTE_PMD_QAT=y,
        CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
        CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y

SUSE11SP2_64 / Linux 3.0.13-0 / 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

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


                 reply	other threads:[~2017-10-04 20:10 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='8a7c36$13432sq@orsmga001.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).