From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/2] next-build: add test app to build
Date: Mon, 18 Dec 2017 15:24:16 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA650FE307F@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <20171218135723.GC15444@bricha3-MOBL3.ger.corp.intel.com>
> From: Richardson, Bruce
> Sent: Monday, December 18, 2017 1:57 PM
> To: Van Haaren, Harry <harry.van.haaren@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [PATCH 0/2] next-build: add test app to build
>
> On Mon, Dec 18, 2017 at 11:53:56AM +0000, Harry van Haaren wrote:
> > This patchset adds the test/test/test app to the Meson build.
> > In doing so, the test app is improved to allow running a unit
> > test by setting an environment variable. This allows the meson
> > test infrastructure to integrate with the DPDK tests. Some nice
> > improvements from the above integration, including debug aids...
> >
> > Run all autotests:
> > $ meson test
> >
>
> meson or ninja?
meson. If I'm understanding correctly the "meson test" command invokes
the ninja test runner, however some of the argument mushing (eg: --gdb)
is performed by meson before launching ninja.
> > Run a specific test:
> > $ meson test ring_perf_autotest
> >
> > Run a specific test multiple times, eg brute-forcing race conditions:
> > $ meson test eventdev_sw_autotest --repeat=3
> >
> > Run a specific test multiple times in gdb, eg to drop to GDB if race
> found:
> > $ meson test eventdev_sw_autotest --repeat=3 --gdb
> >
>
> The "repeat" and "gdb" arguments come built-in in meson, right, not from
> this patchset?
Yes correct, Meson provides this functionality.
<snip>
next prev parent reply other threads:[~2017-12-18 15:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 11:53 Harry van Haaren
2017-12-18 11:53 ` [dpdk-dev] [PATCH 1/2] test: use env variable to run test if set Harry van Haaren
2017-12-18 13:50 ` Bruce Richardson
2017-12-18 14:59 ` Jerin Jacob
2017-12-18 15:24 ` Van Haaren, Harry
2017-12-18 15:41 ` Jerin Jacob
2017-12-18 11:53 ` [dpdk-dev] [PATCH 2/2] meson: add tests app to build Harry van Haaren
2017-12-18 13:55 ` Bruce Richardson
2017-12-18 15:24 ` Van Haaren, Harry
2017-12-20 10:23 ` Bruce Richardson
2017-12-18 13:57 ` [dpdk-dev] [PATCH 0/2] next-build: add test " Bruce Richardson
2017-12-18 15:24 ` Van Haaren, Harry [this message]
2017-12-20 11:16 ` [dpdk-dev] [PATCH v2 " Harry van Haaren
2017-12-20 11:16 ` [dpdk-dev] [PATCH v2 1/2] test: use env variable to run test if set Harry van Haaren
2017-12-20 11:47 ` Bruce Richardson
2017-12-20 11:16 ` [dpdk-dev] [PATCH v2 2/2] meson: add tests app to build Harry van Haaren
2017-12-20 11:57 ` Laatz, Kevin
2017-12-20 12:00 ` Bruce Richardson
2017-12-20 12:20 ` Bruce Richardson
2017-12-20 12:22 ` [dpdk-dev] [PATCH v2 0/2] next-build: add test " Bruce Richardson
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=E923DB57A917B54B9182A2E928D00FA650FE307F@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=bruce.richardson@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).