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] |ERROR| pw 7092 [dpdk-dev] lib: rte_*_create gives NULL/EEXIST on duped name
Date: 18 Sep 2015 11:34:42 -0700 [thread overview]
Message-ID: <2d8c1b$njv7m4@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2620 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork: http://www.dpdk.org/dev/patchwork/patch/7092/
DPDK git baseline: c36a82f045ae362b76af4f2a53af10a2a4d2d20f
Patchwork ID: 7092
http://www.dpdk.org/dev/patchwork/patch/7092/
Submitter: Yoni Fogel <yrobot@amazon.com>
Date: Fri, 18 Sep 2015 10:52:34 -0700
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 75, passed 73, failed 2.
Failed Case List:
Target: x86_64-native-linuxapp-gcc
OS: fedora
Failed DTS case:
acl: http://dpdk.org/browse/tools/dts/tree/test_plans/unit_tests_eal_test_plan.rst
lpm_ipv6: http://dpdk.org/browse/tools/dts/tree/test_plans/unit_tests_lpm_test_plan.rst
DTS Validation Error:
========================================================================================================================
========================================================================================================================
TEST SUITE : TestUnitTestsLpmIpv6
[SUITE_DUT_CMD] make -j -C ./app/test/
-------------------------------------------------------------------------------
Begin: Test Casetest_lpm_ipv6
--------------------------------------------------
FAILED 'Test failed'
--------------------------------------------------
[SUITE_DUT_CMD] echo 4096 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
[SUITE_DUT_CMD] ./app/test/test -n 1 -c ffff
[SUITE_DUT_CMD] lpm6_autotest
[SUITE_DUT_CMD] quit
[SUITE_DUT_CMD] echo 4096 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
End test_lpm_ipv6
-------------------------------------------------------------------------------
[SUITE_TESTER_CMD] killall scapy 2>/dev/null; echo tester
========================================================================================================================
========================================================================================================================
TEST SUITE : TestUnitTestsEal
[SUITE_DUT_CMD] make -j -C ./app/test/
-------------------------------------------------------------------------------
Begin: Test Casetest_acl
--------------------------------------------------
FAILED 'Test failed'
--------------------------------------------------
[SUITE_DUT_CMD] ./app/test/test -n 1 -c ffff
[SUITE_DUT_CMD] acl_autotest
[SUITE_DUT_CMD] quit
End test_acl
-------------------------------------------------------------------------------
[SUITE_TESTER_CMD] killall scapy 2>/dev/null; echo tester
DPDK STV team
reply other threads:[~2015-09-18 18:34 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='2d8c1b$njv7m4@fmsmga001.fm.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).