[dpdk-test-report] | SUCCESS daily Intel builds (20/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]  | SUCCESS daily Intel builds (20/20)
Date: 23 Jan 2019 12:24:22 -0800	[thread overview]
Message-ID: <0590c7$3tp6ej@orsmga001.jf.intel.com> (raw)

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


commit 26e28801ee7d3a18221cc07c3e3e1aa4aad6e1a2
Author: Fan Zhang <roy.fan.zhang@intel.com>
Date:   Fri Jan 18 09:15:57 2019 +0000

    examples/fips_validation: fix physical address


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


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

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

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

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

SUCCESS #12

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

SUCCESS #13

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

FreeBSD11.2/Linux 11.2/Clang6.0.0
Config: x86_64-native-bsdapp-clang
   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

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

SUCCESS #17

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

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

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

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-01-23 20:24 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23 20:24 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-03-04 20:23 sys_stv
2019-03-04  6:50 sys_stv
2019-03-01 20:27 sys_stv
2019-02-28 20:23 sys_stv
2019-02-27 20:25 sys_stv
2019-02-26 20:24 sys_stv
2019-02-25 20:22 sys_stv
2019-02-24 20:21 sys_stv
2019-02-23 20:21 sys_stv
2019-02-22 20:21 sys_stv
2019-02-21 20:21 sys_stv
2019-02-20 20:20 sys_stv
2019-02-19 20:21 sys_stv
2019-02-19  1:29 sys_stv
2019-02-18  3:19 sys_stv
2019-02-14 20:21 sys_stv
2019-02-13 20:21 sys_stv
2019-02-12 20:20 sys_stv
2019-02-12  4:26 sys_stv
2019-02-04 20:21 sys_stv
2019-02-03 20:21 sys_stv
2019-02-02 20:22 sys_stv
2019-02-01 20:21 sys_stv
2019-01-31 20:21 sys_stv
2019-01-31  3:08 sys_stv
2019-01-29 20:24 sys_stv
2019-01-29  1:46 sys_stv
2019-01-28  2:52 sys_stv
2019-01-27 20:23 sys_stv
2019-01-26 20:24 sys_stv
2019-01-25 20:24 sys_stv
2019-01-25  2:21 sys_stv
2019-01-22 20:24 sys_stv
2019-01-22  1:44 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='0590c7$3tp6ej@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).