From: Stephen Hemminger <stephen@networkplumber.org>
To: Felix Moessbauer <felix.moessbauer@siemens.com>
Cc: dev@dpdk.org, william.lam@bytedance.com,
chrisswindle@microsoft.com, aconole@redhat.com,
david.marchand@redhat.com, henning.schild@siemens.com
Subject: Re: [RFC PATCH 1/1] Add basic support for code coverage analysis
Date: Sun, 20 Aug 2023 08:54:36 -0700 [thread overview]
Message-ID: <20230820085436.259809ae@hermes.local> (raw)
In-Reply-To: <20220906164309.1771502-2-felix.moessbauer@siemens.com>
On Tue, 6 Sep 2022 18:43:09 +0200
Felix Moessbauer <felix.moessbauer@siemens.com> wrote:
> This patch adds basic support to get meaningful
> code coverage statistics for some central components.
> To keep things simple, we only focus on the parts that are
> tested as part of the "fast-tests" suite.
> This includes the lib as well as drivers that do not require
> special hardware to be tested.
>
> By providing the gcovr.cfg file in the project root,
> modern versions of meson (>=0.63) can pass that information
> to gcovr, making it possible to configure the coverage target
> of meson.
> This enables us to use the default meson coverage infrastructure
> and customize it for the needs of the DPDK project.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> Acked-by: William Lam <william.lam@bytedance.com>
> Acked-by: Chriss Windle <chrisswindle@microsoft.com>
Not sure why this patch stalled. Seems ok but the set of drivers seems
quite small. Would be good to do it across wider set.
next prev parent reply other threads:[~2023-08-20 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 16:43 [RFC PATCH 0/1] Add support for code-coverage analysis Felix Moessbauer
2022-09-06 16:43 ` [RFC PATCH 1/1] Add basic support for code coverage analysis Felix Moessbauer
2023-08-20 15:54 ` Stephen Hemminger [this message]
2022-09-14 14:29 ` [RFC PATCH 0/1] Add support for code-coverage analysis Aaron Conole
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=20230820085436.259809ae@hermes.local \
--to=stephen@networkplumber.org \
--cc=aconole@redhat.com \
--cc=chrisswindle@microsoft.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=felix.moessbauer@siemens.com \
--cc=henning.schild@siemens.com \
--cc=william.lam@bytedance.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.