From: Luca Boccassi <bluca@debian.org>
To: Bruce Richardson <bruce.richardson@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] test/test: allow taking extra arguments from environment
Date: Fri, 12 Oct 2018 18:42:13 +0100 [thread overview]
Message-ID: <1539366133.8721.47.camel@debian.org> (raw)
In-Reply-To: <20181012153404.46098-1-bruce.richardson@intel.com>
On Fri, 2018-10-12 at 16:34 +0100, Bruce Richardson wrote:
> When running unit tests automatically, either via script, from meson,
> or otherwise, the same set of options may be used for each run, for
> example to set a standard coremask to be used for all tests.
>
> To facilitate this, this patch adds support for the test binary
> taking
> additional EAL parameters from the environment and appending them to
> the
> argc/argv list passed to eal init. This allows parameter modification
> without having to edit test scripts etc.
>
> There are now two environment variables which can be used for running
> tests:
> * DPDK_TEST - (added previously) passes the test name to be run
> automatically rather than running the app
> interactively.
> Used by "meson test" when running tests individually
> or
> as part of a suite.
>
> * DPDK_TEST_PARAMS - new parameter to specify the commandline
> arguments
> to use with the test binary. For example to run a
> test,
> or tests, on only 16 lcores, and to skip pci scan we
> can
> set this to "-l 0-15 --no-pci".
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> doc/guides/rel_notes/release_18_11.rst | 8 ++++++
> test/test/test.c | 34
> +++++++++++++++++++++++++-
> 2 files changed, 41 insertions(+), 1 deletion(-)
Was just thinking that something like this would be useful!
Tested-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2018-10-12 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 15:34 Bruce Richardson
2018-10-12 17:42 ` Luca Boccassi [this message]
2018-11-06 1:59 ` Thomas Monjalon
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=1539366133.8721.47.camel@debian.org \
--to=bluca@debian.org \
--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).