[dpdk-dev] [PATCH] test: allow taking test names from commandline
David Marchand
david.marchand at redhat.com
Fri Apr 9 15:27:17 CEST 2021
On Wed, Jan 27, 2021 at 6:43 PM Bruce Richardson
<bruce.richardson at intel.com> wrote:
>
> While having the ability to run a test based off the DPDK_TEST environment
> variable is useful, it's often easier to specify the test name as a
> commandline parameter to a test binary. This also allows the test runs to
> be saved as part of the shell cmdline history.
I don't get the argument about history:
$ history |grep DPDK_TEST
10615 2021-03-24 10:42:11 ninja-build -C build -j4 &&
DPDK_TEST=logs_autotest ./build/app/test/dpdk-test --no-huge -m 512
--log-level=lib.eal:debug
10636 2021-03-24 10:51:09 ninja-build -C build -j4 &&
DPDK_TEST=logs_autotest ./build/app/test/dpdk-test --no-huge -m 512
--log-level=lib.eal:debug
10653 2021-03-24 11:17:01 ninja-build -C build -j4 &&
DPDK_TEST=kvargs_autotest ./build/app/test/dpdk-test --no-huge -m 512
--log-level=lib.eal:debug
10794 2021-03-25 18:37:48 history |grep DPDK_TEST
>
> This patch adds support for checking all parameters after the EAL ones, and
> running all valid autotests requested - either from DPDK_TEST or on the
> commandline. This also allows multiple tests to be run in a single
> automated session, which is useful for working with components which have
> multiple test suites.
The same could be achieved splitting DPDK_TEST content with spaces,
since test names don't contain one.
--
David Marchand
More information about the dev
mailing list