From: Aaron Conole <aconole@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, Chengwen Feng <fengchengwen@huawei.com>,
Michael Santana <maicolgabriel@hotmail.com>,
Ciara Power <ciara.power@intel.com>
Subject: Re: [PATCH v2 2/2] app/test: invoke all telemetry commands
Date: Fri, 29 Jul 2022 14:04:01 -0400 [thread overview]
Message-ID: <f7ty1wbokxa.fsf@redhat.com> (raw)
In-Reply-To: <20220729124256.1384838-2-david.marchand@redhat.com> (David Marchand's message of "Fri, 29 Jul 2022 14:42:56 +0200")
David Marchand <david.marchand@redhat.com> writes:
> Try and call all possible telemetry commands.
> Each commands is tested with no argument, 0 (for command that accepts
> a single integer like for a port identifier) and z (to catch commands
> not properly validating input).
> Fake cryptodev, dmadev, ethdev, eventdev and rawdev devices are created
> using dummy drivers.
>
> Output of the commands is not checked, the point of this test is mainly
> to catch simple issues and leaks (when coupled with ASan in the CI).
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> Acked-by: Chengwen Feng <fengchengwen@huawei.com>
> ---
Acked-by: Aaron Conole <aconole@redhat.com>
next prev parent reply other threads:[~2022-07-29 18:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 9:54 [PATCH] app/test: invoke all telemetry commands David Marchand
2022-07-29 10:20 ` Bruce Richardson
2022-07-29 11:13 ` David Marchand
2022-07-29 11:28 ` Bruce Richardson
2022-07-29 11:53 ` David Marchand
2022-07-29 13:27 ` Bruce Richardson
2022-07-29 13:42 ` David Marchand
2022-07-29 12:42 ` [PATCH v2 1/2] app/test: load drivers using build directory David Marchand
2022-07-29 12:42 ` [PATCH v2 2/2] app/test: invoke all telemetry commands David Marchand
2022-07-29 18:04 ` Aaron Conole [this message]
2022-08-16 16:20 ` Power, Ciara
2022-08-26 9:42 ` David Marchand
2022-07-29 13:28 ` [PATCH v2 1/2] app/test: load drivers using build directory 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=f7ty1wbokxa.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=ciara.power@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=maicolgabriel@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.