From: sys_stv@intel.com
To: test-report@dpdk.org,ferruh.yigit@intel.com
Subject: [dpdk-test-report] |ERROR| pw 8821 eal: add architecture specific rte_cpuflags.c files
Date: 10 Nov 2015 02:44:58 -0800 [thread overview]
Message-ID: <acb6cf$p85np9@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2950 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork: http://www.dpdk.org/dev/patchwork/patch/8821/
DPDK git baseline: 4c28fb76855edeb03e5bf736dbbafd12cd84ac63
Patchwork ID: 8821
http://www.dpdk.org/dev/patchwork/patch/8821/
Submitter: Ferruh Yigit <ferruh.yigit@intel.com>
Date: Tue, 10 Nov 2015 10:02:07 +0000
Source 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 69, passed 66, failed 3.
Failed Case List:
Target: x86_64-native-linuxapp-gcc
OS: fedora
Failed DTS case:
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
DTS Validation Error:
========================================================================================================================
========================================================================================================================
TEST SUITE : TestMultiprocess
[SUITE_DUT_CMD] make -j -C ./examples/multi_process/
[SUITE_DUT_CMD] cd dpdk
-------------------------------------------------------------------------------
Begin: Test Casetest_multiprocess_simple_mpbasicoperation
--------------------------------------------------
FAILED TIMEOUT on ./examples/multi_process/simple_mp/simple_mp/x86_64-native-linuxapp-gcc/simple_mp -n 1 -c C --proc-type=secondary
--------------------------------------------------
[SUITE_DUT_CMD] ./examples/multi_process/simple_mp/simple_mp/x86_64-native-linuxapp-gcc/simple_mp -n 1 -c 3 --proc-type=primary |tee out
[SUITE_DUT_CMD] ./examples/multi_process/simple_mp/simple_mp/x86_64-native-linuxapp-gcc/simple_mp -n 1 -c C --proc-type=secondary
End test_multiprocess_simple_mpbasicoperation
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Begin: Test Casetest_multiprocess_simple_mploadtest
--------------------------------------------------
FAILED TIMEOUT on lsof -Fp /var/run/.rte_config
--------------------------------------------------
End test_multiprocess_simple_mploadtest
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Begin: Test Casetest_multiprocess_simple_mpnoflag
--------------------------------------------------
FAILED TIMEOUT on lsof -Fp /var/run/.rte_config
--------------------------------------------------
End test_multiprocess_simple_mpnoflag
-------------------------------------------------------------------------------
DPDK STV team
reply other threads:[~2015-11-10 10:45 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='acb6cf$p85np9@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=ferruh.yigit@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).