From: sys_stv@intel.com
To: weichunx.chen@intel.com, haifengx.tang@intel.com,
yufengx.mo@intel.com, yong.liu@intel.com, test-report@dpdk.org,
qian.q.xu@intel.com, waterman.cao@intel.com,
shide.dong@intel.com
Subject: [dpdk-test-report] |SUCCESS| pw 7189 null: export eth_dev_null_create
Date: 25 Sep 2015 07:01:07 -0700 [thread overview]
Message-ID: <c45ac1$jduvs4@orsmga003.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: SUCCESS
Patchwork: http://www.dpdk.org/dev/patchwork/patch/7189/
DPDK git baseline: affc455438f4cbd3b14e2d9a24fbc154e22d68d3
Patchwork ID: 7189
http://www.dpdk.org/dev/patchwork/patch/7189/
Submitter: Tomasz Kulasek <tomaszx.kulasek@intel.com>Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
Date: Fri, 25 Sep 2015 13:24:28 +0000
Compilation:
OS: fedora
Nic: niantic
i686-native-linuxapp-gcc: compile pass
x86_64-native-linuxapp-gcc: compile pass
DTS validation:
OS: fedora
Nic: Niantic
TestType: auto
GCC: 4
x86_64-native-linuxapp-gcc: total 65, passed 61, failed 4.
Failed Case List:
Target: x86_64-native-linuxapp-gcc
OS: fedora
Failed DTS case:
multiprocess_simple_mpapplicationstartup: http://dpdk.org/browse/tools/dts/tree/test_plans/multiprocess_test_plan.rst
multiprocess_simple_mpbasicoperation: http://dpdk.org/browse/tools/dts/tree/test_plans/multiprocess_test_plan.rst
multiprocess_simple_mploadtest: http://dpdk.org/browse/tools/dts/tree/test_plans/multiprocess_test_plan.rst
multiprocess_simple_mpnoflag: http://dpdk.org/browse/tools/dts/tree/test_plans/multiprocess_test_plan.rst
DPDK STV team
reply other threads:[~2015-09-25 14:01 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='c45ac1$jduvs4@orsmga003.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=haifengx.tang@intel.com \
--cc=qian.q.xu@intel.com \
--cc=shide.dong@intel.com \
--cc=test-report@dpdk.org \
--cc=waterman.cao@intel.com \
--cc=weichunx.chen@intel.com \
--cc=yong.liu@intel.com \
--cc=yufengx.mo@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).