DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: Vivian Kong <vivkong@ca.ibm.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] How to run tests
Date: Thu, 9 Aug 2018 17:17:23 +0100	[thread overview]
Message-ID: <20180809161722.GA14668@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <8d982053-4e32-9dbe-fe76-f42bedd52fb5@intel.com>

On Thu, Aug 09, 2018 at 04:54:36PM +0100, Burakov, Anatoly wrote:
> On 09-Aug-18 2:54 PM, Vivian Kong wrote:
> > Thanks Anatoly.
> > 
> > Is there a set of tests I can run to verify the build?
> 
> Generally, most unit tests in the test app will do what you require.
> Additionally, if you're using make build system, you can run "make test" and
> it'll run an autotest script. Some tests may fail for various reasons
> (additional setup requirements for KNI tests, multiprocess issues affecting
> EAL flags and multiprocess autotests...), but generally that command can be
> used to "verify the build".
> 
> That said, it is by no means an exhaustive test, because most of DPDK
> functionality of interest will require setting up traffic forwarding - unit
> tests do very limited testing of that for obvious reasons.
> 

Just FYI:
As well as "make test", for meson builds you can also use "meson test", or
"meson test <testname>" to run just one specific test.

  reply	other threads:[~2018-08-09 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08 20:10 Vivian Kong
2018-08-09  8:48 ` Burakov, Anatoly
2018-08-09 14:15   ` Vivian Kong
     [not found]   ` <OFCA81C194.0496E304-ON852582E4.004C3334-852582E4.004C5F6D@notes.na.collabserv.com>
2018-08-09 15:54     ` Burakov, Anatoly
2018-08-09 16:17       ` Bruce Richardson [this message]
2018-08-09 16:42         ` Vivian Kong

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=20180809161722.GA14668@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=vivkong@ca.ibm.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).