From: sys_stv@intel.com
To: test-report@dpdk.org,jerin.jacob@caviumnetworks.com
Subject: [dpdk-test-report] |ERROR| pw 9061-9064 mk: add xgene1 machine target based on armv8-a
Date: 23 Nov 2015 11:34:49 -0800 [thread overview]
Message-ID: <edcf24$i1qbse@FMSMGA003.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1561 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork: http://www.dpdk.org/dev/patchwork/patch/9064/
DPDK git baseline: 46454f16d548afc202f157751365088910dcf0e7
Patchwork ID: 9061-9064
http://www.dpdk.org/dev/patchwork/patch/9064/
Submitter: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Date: Tue, 24 Nov 2015 00:15:38 +0530
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 79, passed 78, failed 1.
Failed Case List:
Target: x86_64-native-linuxapp-gcc
OS: fedora
Failed DTS case:
link_bonding: http://dpdk.org/browse/tools/dts/tree/test_plans/unit_tests_eal_test_plan.rst
DTS Validation Error:
========================================================================================================================
========================================================================================================================
TEST SUITE : TestUnitTestsEal
[SUITE_DUT_CMD] make -j -C ./app/test/
-------------------------------------------------------------------------------
Begin: Test Casetest_link_bonding
--------------------------------------------------
FAILED 'Test failed'
--------------------------------------------------
[SUITE_DUT_CMD] ./app/test/test -n 1 -c ffff
[SUITE_DUT_CMD] link_bonding_autotest
[SUITE_DUT_CMD] quit
End test_link_bonding
-------------------------------------------------------------------------------
DPDK STV team
next reply other threads:[~2015-11-23 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 19:34 sys_stv [this message]
2015-11-25 13:43 ` Jerin Jacob
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='edcf24$i1qbse@FMSMGA003.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=jerin.jacob@caviumnetworks.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).