automatic DPDK test reports
 help / color / mirror / Atom feed
From: "Polehn, Mike A" <mike.a.polehn@intel.com>
To: sys_stv <sys_stv@intel.com>,
	"test-report@dpdk.org" <test-report@dpdk.org>
Subject: Re: [dpdk-test-report] |ERROR| pw 8595 Eth driver optimization: Prefetch variable structure
Date: Wed, 4 Nov 2015 15:00:07 +0000	[thread overview]
Message-ID: <745DB4B8861F8E4B9849C970520ABBF1497510B9@ORSMSX102.amr.corp.intel.com> (raw)
In-Reply-To: <e9ea37$p3dhjm@orsmga002.jf.intel.com>

Definitely have an error in the test program, or in the base code tested, but not the code change tested.

Mike

-----Original Message-----
From: sys_stv 
Sent: Wednesday, November 4, 2015 6:56 AM
To: test-report@dpdk.org; Polehn, Mike A
Subject: |ERROR| pw 8595 Eth driver optimization: Prefetch variable structure

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 

      reply	other threads:[~2015-11-04 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 14:55 sys_stv
2015-11-04 15:00 ` Polehn, Mike A [this message]

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=745DB4B8861F8E4B9849C970520ABBF1497510B9@ORSMSX102.amr.corp.intel.com \
    --to=mike.a.polehn@intel.com \
    --cc=sys_stv@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).