From: Bruce Richardson <bruce.richardson@intel.com>
To: Harry van Haaren <harry.van.haaren@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 0/2] next-build: add test app to build
Date: Wed, 20 Dec 2017 12:22:13 +0000 [thread overview]
Message-ID: <20171220122213.GD5200@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <1513768592-112485-1-git-send-email-harry.van.haaren@intel.com>
On Wed, Dec 20, 2017 at 11:16:30AM +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
>
> 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
>
>
> Meson also provides various options to "wrap" the test binary,
> which can be used for running in eg: Valgrind or other tools. For
> more information about Meson and its testing capabilities, see here:
> http://mesonbuild.com/Unit-tests.html
>
> Cheers, -Harry
>
> ---
>
> v2: updated patch 2/2 to SPDX license
>
> Harry van Haaren (2):
> test: use env variable to run test if set
> meson: add tests app to build
>
Applied to dpdk-next-build
Thanks,
/Bruce
prev parent reply other threads:[~2017-12-20 12:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 11:53 [dpdk-dev] [PATCH " 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
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 ` Bruce Richardson [this message]
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=20171220122213.GD5200@bricha3-MOBL3.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.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).