From: sys_stv@intel.com
To: test-report@dpdk.org,mike.a.polehn@intel.com
Subject: [dpdk-test-report] |ERROR| pw 8595 Eth driver optimization: Prefetch variable structure
Date: 04 Nov 2015 06:55:53 -0800 [thread overview]
Message-ID: <e9ea37$p3dhjm@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork: http://www.dpdk.org/dev/patchwork/patch/8595/
DPDK git baseline: 00c14643821c619375bf04264cf3afeb899b1e7a
Patchwork ID: 8595
http://www.dpdk.org/dev/patchwork/patch/8595/
Submitter: "Polehn, Mike A" <mike.a.polehn@intel.com>
Date: Tue, 3 Nov 2015 15:00:15 +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 79, passed 78, failed 1.
Failed Case List:
Target: x86_64-native-linuxapp-gcc
OS: fedora
Failed DTS case:
malloc: 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_malloc
--------------------------------------------------
FAILED TIMEOUT on malloc_autotest
--------------------------------------------------
[SUITE_DUT_CMD] ./app/test/test -n 1 -c ffff
[SUITE_DUT_CMD] malloc_autotest
End test_malloc
-------------------------------------------------------------------------------
DPDK STV team
next reply other threads:[~2015-11-04 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 14:55 sys_stv [this message]
2015-11-04 15:00 ` Polehn, Mike A
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='e9ea37$p3dhjm@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=mike.a.polehn@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).