[dpdk-dev] [PATCH 0/2] next-build: add test app to build

Van Haaren, Harry harry.van.haaren at intel.com
Mon Dec 18 16:24:16 CET 2017


> From: Richardson, Bruce
> Sent: Monday, December 18, 2017 1:57 PM
> To: Van Haaren, Harry <harry.van.haaren at intel.com>
> Cc: dev at 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>


More information about the dev mailing list