From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
Aaron Conole <aconole@redhat.com>
Subject: Re: [PATCH v4] app/test: add support for skipping tests
Date: Mon, 2 Oct 2023 11:20:23 +0200 [thread overview]
Message-ID: <CAJFAV8wDy10eVFtZk8BvfeUCcwrrCW2WDgDow_vOgkQ9xTQcDA@mail.gmail.com> (raw)
In-Reply-To: <f7tcyy6w75n.fsf@redhat.com>
On Mon, Sep 25, 2023 at 6:27 PM Aaron Conole <aconole@redhat.com> wrote:
> Bruce Richardson <bruce.richardson@intel.com> writes:
>
> > When called from automated tools, like meson test, it is often useful to
> > skip tests in a test suite, without having to alter the test build. To
> > do so, we add support for DPDK_TEST_SKIP environment variable, where one
> > can provide a comma-separated list of tests. When the test binary is
> > called to run one of the tests on the list via either cmdline parameter
> > or environment variable (as done with meson test), the test will not
> > actually be run, but will be reported skipped.
> >
> > Example run:
> > $ DPDK_TEST_SKIP=dump_devargs,dump_ring meson test --suite=debug-tests
> > ...
> > 1/9 DPDK:debug-tests / dump_devargs SKIP 1.11s
> > 2/9 DPDK:debug-tests / dump_log_types OK 1.06s
> > 3/9 DPDK:debug-tests / dump_malloc_heaps OK 1.11s
> > 4/9 DPDK:debug-tests / dump_malloc_stats OK 1.07s
> > 5/9 DPDK:debug-tests / dump_mempool OK 1.11s
> > 6/9 DPDK:debug-tests / dump_memzone OK 1.06s
> > 7/9 DPDK:debug-tests / dump_physmem OK 1.13s
> > 8/9 DPDK:debug-tests / dump_ring SKIP 1.04s
> > 9/9 DPDK:debug-tests / dump_struct_sizes OK 1.10s
> >
> > Ok: 7
> > Expected Fail: 0
> > Fail: 0
> > Unexpected Pass: 0
> > Skipped: 2
> > Timeout: 0
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > Acked-by: Thomas Monjalon <thomas@monjalon.net>
> Acked-by: Aaron Conole <aconole@redhat.com>
Applied, thanks.
--
David Marchand
next prev parent reply other threads:[~2023-10-02 9:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 10:58 [RFC PATCH] " Bruce Richardson
2023-08-29 9:34 ` Thomas Monjalon
2023-08-29 13:27 ` Aaron Conole
2023-08-29 13:39 ` Bruce Richardson
2023-08-31 10:06 ` [PATCH v2] " Bruce Richardson
2023-08-31 10:18 ` [PATCH v3] " Bruce Richardson
2023-08-31 13:58 ` Bruce Richardson
2023-09-14 15:16 ` [PATCH v4] " Bruce Richardson
2023-09-25 16:26 ` Aaron Conole
2023-10-02 9:20 ` David Marchand [this message]
2023-10-03 20:22 ` Patrick Robb
2023-10-04 15:13 ` Aaron Conole
2023-10-09 20:03 ` Patrick Robb
2023-10-20 15:02 ` Patrick Robb
2023-10-20 15:08 ` 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=CAJFAV8wDy10eVFtZk8BvfeUCcwrrCW2WDgDow_vOgkQ9xTQcDA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).