From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: cota@braap.org, famz@redhat.com, f4bug@amsat.org,
richard.henderson@linaro.org, balrogg@gmail.com,
aurelien@aurel32.net, agraf@suse.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v1 08/10] build-system: add coverage-report target
Date: Fri, 29 Jun 2018 12:48:03 +0100 [thread overview]
Message-ID: <20180629114803.GO27016@redhat.com> (raw)
In-Reply-To: <20180625111935.26108-9-alex.bennee@linaro.org>
On Mon, Jun 25, 2018 at 12:19:33PM +0100, Alex Bennée wrote:
> This will build a coverage report under the current directory in
> reports/coverage. At the users option a report can be generated by
> directly invoking something like:
>
> make foo/bar/coverage-report.html
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> Makefile | 13 +++++++++++++
> docs/devel/testing.rst | 11 ++++++++---
> 2 files changed, 21 insertions(+), 3 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 2b3413a5ba..68af7b5d7c 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -986,6 +986,16 @@ docs/interop/qemu-qmp-ref.dvi docs/interop/qemu-qmp-ref.html \
> docs/interop/qemu-qmp-ref.txt docs/interop/qemu-qmp-ref.7: \
> docs/interop/qemu-qmp-ref.texi docs/interop/qemu-qmp-qapi.texi
>
> +# Reports/Analysis
> +
> +%/coverage-report.html:
> + @mkdir -p $*
> + $(call quiet-command,\
> + gcovr -p --html --html-details -o $@, \
> + "GEN", "coverage-report.html")
> +
> +.PHONY: coverage-report
> +coverage-report: $(CURDIR)/reports/coverage/coverage-report.html
>
> ifdef CONFIG_WIN32
>
> @@ -1095,6 +1105,9 @@ endif
> @echo 'Documentation targets:'
> @echo ' html info pdf txt'
> @echo ' - Build documentation in specified format'
> +ifdef CONFIG_GCOV
> + @echo ' coverage-report - Create code coverage report'
> +endif
> @echo ''
> ifdef CONFIG_WIN32
> @echo 'Windows targets:'
> diff --git a/docs/devel/testing.rst b/docs/devel/testing.rst
> index a3652aea14..9dcdd19260 100644
> --- a/docs/devel/testing.rst
> +++ b/docs/devel/testing.rst
> @@ -166,9 +166,14 @@ If you want to gather coverage information on a single test the ``make
> clean-coverage`` target can be used to any existing coverage
> information before running a single test.
>
> -Reports can be obtained by running ``gcov`` command
> -on the output files under ``$build_dir/tests/``, please read the
> -``gcov`` documentation for more information.
> +You can generate a HTML coverage report by executing ``make
> +coverage-report`` which will generate into
I think it reads slightly better with
s/generate into/create/
> +./reports/coverage/coverage-report.html. If you want to generate it
s/generate/create/
> +elsewhere simply execute ``make /foo/bar/baz/coverage-report.html``.
> +
> +Further analysis can be conducted by running the ``gcov`` command
> +directly on the various .gcda output files. Please read the ``gcov``
> +documentation for more information.
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-06-29 11:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 11:19 [Qemu-devel] [PATCH v1 00/10] Travis updates and code coverage tweaks Alex Bennée
2018-06-25 11:19 ` [Qemu-devel] [PATCH v1 01/10] travis: do not waste time cloning unused submodules Alex Bennée
2018-06-29 11:41 ` Daniel P. Berrangé
2018-06-25 11:19 ` [Qemu-devel] [PATCH v1 02/10] travis: test out-of-tree builds Alex Bennée
2018-06-29 11:42 ` Daniel P. Berrangé
2018-06-25 11:19 ` [Qemu-devel] [PATCH v1 03/10] build-system: remove per-test GCOV reporting Alex Bennée
2018-06-29 11:43 ` Daniel P. Berrangé
2018-06-25 11:19 ` [Qemu-devel] [PATCH v1 04/10] .gitignore: add .gcov files Alex Bennée
2018-06-29 11:43 ` Daniel P. Berrangé
2018-06-25 11:19 ` [Qemu-devel] [PATCH v1 05/10] docker: add gcovr to travis image Alex Bennée
2018-06-25 11:32 ` Philippe Mathieu-Daudé
2018-06-29 11:44 ` Daniel P. Berrangé
2018-06-25 11:19 ` [Qemu-devel] [PATCH v1 06/10] travis: add gcovr summary for GCOV build Alex Bennée
2018-06-29 11:45 ` Daniel P. Berrangé
2018-06-25 11:19 ` [Qemu-devel] [PATCH v1 07/10] build-system: add clean-coverage target Alex Bennée
2018-06-29 11:46 ` Daniel P. Berrangé
2018-06-25 11:19 ` [Qemu-devel] [PATCH v1 08/10] build-system: add coverage-report target Alex Bennée
2018-06-29 11:48 ` Daniel P. Berrangé [this message]
2018-06-25 11:19 ` [Qemu-devel] [PATCH v1 09/10] linux-user: introduce preexit_cleanup Alex Bennée
2018-06-25 11:34 ` Philippe Mathieu-Daudé
2018-06-29 11:48 ` Daniel P. Berrangé
2018-06-29 14:22 ` Laurent Vivier
2018-06-25 11:19 ` [Qemu-devel] [PATCH v1 10/10] linux-user: add gcov support to preexit_cleanup Alex Bennée
2018-06-25 11:38 ` Philippe Mathieu-Daudé
2018-06-25 12:47 ` Alex Bennée
2018-07-02 2:04 ` [Qemu-devel] [PATCH v1 00/10] Travis updates and code coverage tweaks no-reply
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=20180629114803.GO27016@redhat.com \
--to=berrange@redhat.com \
--cc=agraf@suse.de \
--cc=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=balrogg@gmail.com \
--cc=cota@braap.org \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 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.