DPDK patches and discussions
 help / color / mirror / Atom feed
From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: dev@dpdk.org
Cc: william.lam@bytedance.com, chrisswindle@microsoft.com,
	aconole@redhat.com, david.marchand@redhat.com,
	henning.schild@siemens.com,
	Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [RFC PATCH 0/1] Add support for code-coverage analysis
Date: Tue,  6 Sep 2022 18:43:08 +0200	[thread overview]
Message-ID: <20220906164309.1771502-1-felix.moessbauer@siemens.com> (raw)

This patch has been developed as part of the DPDK Userspace Summit Hackathon.
It provides a PoC for code-coverage analysis for the DPDK project.

To generate the report, a developer simply follows the official
meson coverage workflow, described in [1].
In doing so, both an HTML report, as well as an XML version is generated
for further processing.

In short, the following steps are required:

- install gcovr
- meson -Db_coverage=true build-cov
- meson compile -C build-cov
- meson test -C build-cov --suite fast-tests
- ninja coverage -C build-cov

[1] https://mesonbuild.com/howtox.html#producing-a-coverage-report

Best regards,
Felix Moessbauer
Siemens AG

Felix Moessbauer (1):
  Add basic support for code coverage analysis

 gcovr.cfg | 8 ++++++++
 1 file changed, 8 insertions(+)
 create mode 100644 gcovr.cfg

-- 
2.30.2


             reply	other threads:[~2022-09-06 16:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06 16:43 Felix Moessbauer [this message]
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
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=20220906164309.1771502-1-felix.moessbauer@siemens.com \
    --to=felix.moessbauer@siemens.com \
    --cc=aconole@redhat.com \
    --cc=chrisswindle@microsoft.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --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 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).