From: "Vivian Kong" <vivkong@ca.ibm.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] How to run tests
Date: Thu, 9 Aug 2018 10:15:28 -0400 [thread overview]
Message-ID: <OF86B330B6.08954F54-ON852582E4.004E4316-852582E4.004E520D@notes.na.collabserv.com> (raw)
In-Reply-To: <3fa3162e-9440-a957-4aa1-0f437e245ba2@intel.com>
Thanks Anatoly. I can find the test application now.
Is there a set of tests I can run to verify the build?
Regards,
Vivian Kong
Linux on z Systems Open Source Ecosystem
IBM Canada Toronto Lab
"Burakov, Anatoly" <anatoly.burakov@intel.com> wrote on 2018/08/09 04:48:21
AM:
> On 08-Aug-18 9:10 PM, Vivian Kong wrote:
> >
> >
> > Hi everyone,
> >
> > Got a newbie question - I was able to build the source with `make
install
> > DESTDIR=~/dpdk-install T=x86_64-native-linuxapp-gcc`. How do I go
about
> > running the tests? I looked into the directory
> > "x86_64-native-linuxapp-gcc" but I didn't see the "app/test"
executable.
> > Am I missing something in my make command?
> >
> > Thanks for your help.
> >
> > Regards,
> >
> > Vivian Kong
> > Linux on z Systems Open Source Ecosystem
> > IBM Canada Toronto Lab
> >
>
> Hi,
>
> If you're using make build system, you need to run "make test-build" to
> build the test application. Then, you'll be able to run the test
> application.
>
> With meson build system, the test application is built by default, and
> will be located at <your build dir>/test/test/dpdk-test.
>
> --
> Thanks,
> Anatoly
>
next prev parent reply other threads:[~2018-08-09 14:16 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 [this message]
[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
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=OF86B330B6.08954F54-ON852582E4.004E4316-852582E4.004E520D@notes.na.collabserv.com \
--to=vivkong@ca.ibm.com \
--cc=anatoly.burakov@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).