From: "Alex Bennée" <alex.bennee@linaro.org>
To: peter.maydell@linaro.org
Cc: qemu-devel@nongnu.org, cota@braap.org, famz@redhat.com,
berrange@redhat.com, f4bug@amsat.org,
richard.henderson@linaro.org, balrogg@gmail.com,
aurelien@aurel32.net, agraf@suse.de,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [Qemu-devel] [PULL 08/20] build-system: add coverage-report target
Date: Tue, 3 Jul 2018 11:14:32 +0100 [thread overview]
Message-ID: <20180703101444.23778-9-alex.bennee@linaro.org> (raw)
In-Reply-To: <20180703101444.23778-1-alex.bennee@linaro.org>
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>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
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 7f04ca104e..5e19cd50da 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 delete 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 create
+./reports/coverage/coverage-report.html. If you want to create it
+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.
QEMU iotests
============
--
2.17.1
next prev parent reply other threads:[~2018-07-03 10:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 10:14 [Qemu-devel] [PULL 00/20] Travis, Code Coverage and Cross Build updates Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 01/20] travis: do not waste time cloning unused submodules Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 02/20] travis: test out-of-tree builds Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 03/20] build-system: remove per-test GCOV reporting Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 04/20] .gitignore: add .gcov files Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 05/20] docker: add gcovr to travis image Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 06/20] travis: add gcovr summary for GCOV build Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 07/20] build-system: add clean-coverage target Alex Bennée
2018-07-03 10:14 ` Alex Bennée [this message]
2018-07-03 10:14 ` [Qemu-devel] [PULL 09/20] linux-user: introduce preexit_cleanup Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 10/20] linux-user: add gcov support to preexit_cleanup Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 11/20] docker: filter out linux-user builds for mingw Alex Bennée
2018-07-03 13:44 ` Paolo Bonzini
2018-07-03 19:45 ` Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 12/20] docker: ubuntu: Update the package list before installing new ones Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 13/20] docker: ubuntu: Use SDL2 Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 14/20] docker: Clean the MXE base image Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 15/20] docker: Do not run tests in 'intermediate' images Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 16/20] docker: drop QEMU build-dep from bootstrap Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 17/20] docker: debian-bootstrap.pre allow customising of variant/url Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 18/20] docker: add special handling for FROM:debian-%-user targets Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 19/20] docker: add special rule for deboostrapped images Alex Bennée
2018-07-03 10:14 ` [Qemu-devel] [PULL 20/20] docker: add linux-user powered cross builder for QEMU Alex Bennée
2018-07-03 13:46 ` [Qemu-devel] [PULL 00/20] Travis, Code Coverage and Cross Build updates Paolo Bonzini
2018-07-03 19:45 ` Alex Bennée
2018-07-04 10:15 ` Alex Bennée
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=20180703101444.23778-9-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=agraf@suse.de \
--cc=aurelien@aurel32.net \
--cc=balrogg@gmail.com \
--cc=berrange@redhat.com \
--cc=cota@braap.org \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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).