From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xinfengx.zhao@intel.com, zhaoyan.chen@intel.com, peipeix.lu@intel.com
Subject: [dpdk-test-report] |SUCCESS| pw38240[dpdk-dev, v4, 06/16] ethdev: remove C99 flexible arrays from flow API
Date: 20 Apr 2018 05:12:07 -0700 [thread overview]
Message-ID: <0590c7$1f4svk@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1927 bytes --]
Test-Label: Intel-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/38240
_Compilation OK_
Submitter: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Date: 2018-04-16 16:22:40
DPDK git baseline: Repo:dpdk-next-net, CommitID: 22f9945b76ebc7f6f3075b62344450811d0c3617
Build Summary: 15 Builds Done, 15 Successful, 0 Failures
Test environment and configuration as below:
OS: FC25
Kernel Version: 4.9.13-100.fc24.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (GCC) 6.2.1 20160916 (Red Hat 6.2.1-2)
Clang Version: 3.8.0 (tags/RELEASE_380/final)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-debug
OS: FC24
Kernel Version: 4.9.13-100.fc24.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (GCC) 6.2.1 20160916 (Red Hat 6.2.1-2)
Clang Version: 3.8.0 (tags/RELEASE_380/final)
x86_64-native-linuxapp-gcc-shared
i686-native-linuxapp-gcc
x86_64-native-linuxapp-clang
OS: CENTOS
Kernel Version: 3.10.0-514.10.2.el7.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc-shared
i686-native-linuxapp-gcc
x86_64-native-linuxapp-gcc
OS: UB1604
Kernel Version: 4.4.0-81-generic
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609
Clang Version: 3.8.0-2ubuntu4 (tags/RELEASE_380/final)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-shared
i686-native-linuxapp-gcc
x86_64-native-linuxapp-clang
OS: FreeBSD
Kernel Version: 10.3-RELEASE
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz (2294.75-MHz K8-class CPU)
GCC Version: gcc (FreeBSD Ports Collection) 4.8.5
Clang Version: 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc
DPDK STV team
reply other threads:[~2018-04-20 12:12 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='0590c7$1f4svk@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=peipeix.lu@intel.com \
--cc=test-report@dpdk.org \
--cc=xinfengx.zhao@intel.com \
--cc=zhaoyan.chen@intel.com \
/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).