From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: David Marchand <david.marchand@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/2] app/test: filter out unavailable tests
Date: Fri, 15 Jul 2016 16:30:35 +0200 [thread overview]
Message-ID: <3461958.LeeMAe6FG1@xps13> (raw)
In-Reply-To: <CALwxeUvEdifcEaP3-otzy8mNrOk9x8pS0EZo26iyn2PdCSeApg@mail.gmail.com>
2016-07-15 16:23, David Marchand:
> On Wed, Jul 13, 2016 at 11:24 PM, Thomas Monjalon
> <thomas.monjalon@6wind.com> wrote:
> > Some tests can fail to run because they are not compiled.
> > It has been more visible recently when the PCI test became disabled
> > in the default configuration because of dependency on libarchive:
> > PCI autotest: Fail [Not found]
> >
> > The autotest script catch them and do not count them as an error anymore:
> > PCI autotest: Skipped [Not Available]
> >
> > The commands dump_ring and dump_mempool are removed from the autotest list
> > because they are some internal commands but not some registered tests.
> > Thus they cannot be parsed as available test commands.
> >
> > Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
>
> Suggested-by: David Marchand <david.marchand@6wind.com>
Thanks for giving me the idea of the nm trick.
> and I trust you for the python ;-)
You should not ;)
next prev parent reply other threads:[~2016-07-15 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 21:24 [dpdk-dev] [PATCH 1/2] app/test: rework command registration Thomas Monjalon
2016-07-13 21:24 ` [dpdk-dev] [PATCH 2/2] app/test: filter out unavailable tests Thomas Monjalon
2016-07-15 14:23 ` David Marchand
2016-07-15 14:30 ` Thomas Monjalon [this message]
2016-07-15 15:25 ` Thomas Monjalon
2016-07-14 17:25 ` [dpdk-dev] [dpdk-dev, 1/2] app/test: rework command registration viktorin
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=3461958.LeeMAe6FG1@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=david.marchand@6wind.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).