DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Hunt, David" <david.hunt@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK ArmV7 autotests
Date: Tue, 10 Nov 2015 11:30:30 +0100	[thread overview]
Message-ID: <7285692.g8AiFBK0OF@xps13> (raw)
In-Reply-To: <5641C561.6020107@intel.com>

2015-11-10 10:22, Hunt, David:
> On 09/11/2015 17:46, Jan Viktorin wrote:
>  > Here is the log. You an see, that many tests fail just because
>  > of the missing hugetlb support. This is strange as I modified the
>  > autotest_runner.py to inject "--no-huge --no-pci" options when it
>  > detects armv7 architecture.
> 
> I think publishing these test results to the mailing list confuses 
> matters somewhat. The tests are not tuned for armv7, and there are many 
> false negatives, giving the impression that the results are worse than 
> they actually should be.
> 
> The tests need to be analysed to see if they respect the --no-huge and 
> --no-pci flags correctly, I suspect some tests are being run even though 
> these flags are enabled.
> 
> I believe enough of the tests pass to allow the initial version of the 
> patch set to be accepted. We can look at the failing cases later, and 
> improve the test suite as time goes on.

I agree.
The unit tests are know to require some refactoring.
I suggest to continue ARM integration while checking how to fix the
unit tests later. Maybe that Declan has some ideas or plans about the tests.

  reply	other threads:[~2015-11-10 10:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5640CB56.4080506@intel.com>
2015-11-09 17:12 ` Jan Viktorin
2015-11-09 17:26   ` Hunt, David
2015-11-09 17:46     ` Jan Viktorin
2015-11-10 10:22       ` Hunt, David
2015-11-10 10:30         ` Thomas Monjalon [this message]
2015-11-10 12:45           ` 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=7285692.g8AiFBK0OF@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=david.hunt@intel.com \
    --cc=dev@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).