From: "Zhang, XuemingX" <xuemingx.zhang@intel.com>
To: "'announce@dpdk.org'" <announce@dpdk.org>, "'ci@dpdk.org'" <ci@dpdk.org>
Cc: "'test-report@dpdk.org'" <test-report@dpdk.org>,
DPDK_SW_ENG <dpdk_sw_eng@intel.com>,
NPG SW Core Tools PRC <npg.sw.core.tools.prc@intel.com>
Subject: Re: [dpdk-ci] Announcement About Daily Build System Replacement
Date: Wed, 23 Jan 2019 03:30:35 +0000 [thread overview]
Message-ID: <4E0B5ACD6F83CA4CB9C3F1B1F2F0ED5A0B2FB418@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <4E0B5ACD6F83CA4CB9C3F1B1F2F0ED5A0B2F457C@SHSMSX101.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
Hi all:
As the system version is updated, Most of the 52 platforms built daily are too old to meet our needs.
After deliberation, we selected 20 platforms for daily build. Now, The 20 platforms build has released the report on January 22, 2019
The new daily build system includes the following platforms info:
OS
Kernel
Target
1
OpenSUSE15
4.12.14-lp150.12.16-default
GCC 7.3.1
2
RHEL74
3.10.0-693.el7.x86_64
GCC 4.8.5
3
RHEL75
3.10.0-862.el7.x86_64
GCC 4.8.5
4
CENTOS74
3.10.0-862.11.6.el7.x86_64
GCC 4.8.5
5
CENTOS75
3.10.0-862.11.6.el7.x86_64
GCC 4.8.5
6
FC28
4.16.3-301.fc28.x86_64
GCC 8.0.1
7
FC28
4.16.3-301.fc28.x86_64
Clang 6.0.1
8
FC28
4.16.3-301.fc28.x86_64
ICC 19.0.0
9
UBT144_32
3.13.0-32-generic
GCC 4.8.4
10
UBT144_64
4.2.0-27-generic
GCC 4.8.4
11
UBT164_64
4.4.0-47-generic
GCC 5.4.0
12
UBT164_32
4.4.0-131-generic
GCC 5.4.0
13
UBT1804
4.15.0-20-generic
GCC 7.3.0
14
UBT1804
Linux 4.15.0-20-generic
Clang 6.0.0
15
UBT1804
Linux 4.15.0-20-generic
ICC 19.0.0
16
UBT1810
Linux 4.18.0-10-generic
GCC 8.2.0-7
17
FreeBSD11.2
11.2-RELEASE
GCC 6.4.0
18
FreeBSD11.2
11.2-RELEASE
Clang 6.0.0
19
FreeBSD12.0
12.0-RC3
GCC 7.3.0
20
FreeBSD12.0
12.0-RC3
Clang 6.0.1
[-- Attachment #2: Type: text/html, Size: 36785 bytes --]
parent reply other threads:[~2019-01-23 3:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4E0B5ACD6F83CA4CB9C3F1B1F2F0ED5A0B2F457C@SHSMSX101.ccr.corp.intel.com>]
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=4E0B5ACD6F83CA4CB9C3F1B1F2F0ED5A0B2FB418@SHSMSX101.ccr.corp.intel.com \
--to=xuemingx.zhang@intel.com \
--cc=announce@dpdk.org \
--cc=ci@dpdk.org \
--cc=dpdk_sw_eng@intel.com \
--cc=npg.sw.core.tools.prc@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).