From: "Alex Bennée" <alex.bennee@linaro.org>
To: 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
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: [Qemu-devel] [PATCH v1 03/10] build-system: remove per-test GCOV reporting
Date: Mon, 25 Jun 2018 12:19:28 +0100 [thread overview]
Message-ID: <20180625111935.26108-4-alex.bennee@linaro.org> (raw)
In-Reply-To: <20180625111935.26108-1-alex.bennee@linaro.org>
I'm not entirely sure who's using this information and certainly in a
CI environment it just washes over as additional noise. Later patches
will provide new reporting options so a user who wants to analyse
individual tests will be able to use that to get the information.
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>
---
docs/devel/testing.rst | 11 +++++------
tests/Makefile.include | 10 ----------
2 files changed, 5 insertions(+), 16 deletions(-)
diff --git a/docs/devel/testing.rst b/docs/devel/testing.rst
index f33e5a8423..66ef219f69 100644
--- a/docs/devel/testing.rst
+++ b/docs/devel/testing.rst
@@ -158,12 +158,11 @@ rarely used. See "QEMU iotests" section below for more information.
GCC gcov support
----------------
-``gcov`` is a GCC tool to analyze the testing coverage by instrumenting the
-tested code. To use it, configure QEMU with ``--enable-gcov`` option and build.
-Then run ``make check`` as usual. There will be additional ``gcov`` output as
-the testing goes on, showing the test coverage percentage numbers per analyzed
-source file. More detailed reports can be obtained by running ``gcov`` command
-on the output files under ``$build_dir/tests/``, please read the ``gcov``
+``gcov`` is a GCC tool to analyze the testing coverage by
+instrumenting the tested code. To use it, configure QEMU with
+``--enable-gcov`` option and build. Then run ``make check`` as usual.
+Reports can be obtained by running ``gcov`` command on the output
+files under ``$build_dir/tests/``, please read the ``gcov``
documentation for more information.
QEMU iotests
diff --git a/tests/Makefile.include b/tests/Makefile.include
index e8bb2d8f66..756474814a 100644
--- a/tests/Makefile.include
+++ b/tests/Makefile.include
@@ -891,26 +891,16 @@ GCOV_OPTIONS = -n $(if $(V),-f,)
.PHONY: $(patsubst %, check-qtest-%, $(QTEST_TARGETS))
$(patsubst %, check-qtest-%, $(QTEST_TARGETS)): check-qtest-%: subdir-%-softmmu $(check-qtest-y)
- $(if $(CONFIG_GCOV),@rm -f *.gcda */*.gcda */*/*.gcda */*/*/*.gcda,)
$(call quiet-command,QTEST_QEMU_BINARY=$*-softmmu/qemu-system-$* \
QTEST_QEMU_IMG=qemu-img$(EXESUF) \
MALLOC_PERTURB_=$${MALLOC_PERTURB_:-$$(( $${RANDOM:-0} % 255 + 1))} \
gtester $(GTESTER_OPTIONS) -m=$(SPEED) $(check-qtest-$*-y) $(check-qtest-generic-y),"GTESTER","$@")
- $(if $(CONFIG_GCOV),@for f in $(gcov-files-$*-y) $(gcov-files-generic-y); do \
- echo Gcov report for $$f:;\
- $(GCOV) $(GCOV_OPTIONS) $$f -o `dirname $$f`; \
- done,)
.PHONY: $(patsubst %, check-%, $(check-unit-y) $(check-speed-y))
$(patsubst %, check-%, $(check-unit-y) $(check-speed-y)): check-%: %
- $(if $(CONFIG_GCOV),@rm -f *.gcda */*.gcda */*/*.gcda */*/*/*.gcda,)
$(call quiet-command, \
MALLOC_PERTURB_=$${MALLOC_PERTURB_:-$$(( $${RANDOM:-0} % 255 + 1))} \
gtester $(GTESTER_OPTIONS) -m=$(SPEED) $*,"GTESTER","$*")
- $(if $(CONFIG_GCOV),@for f in $(gcov-files-$(subst tests/,,$*)-y) $(gcov-files-generic-y); do \
- echo Gcov report for $$f:;\
- $(GCOV) $(GCOV_OPTIONS) $$f -o `dirname $$f`; \
- done,)
# gtester tests with XML output
--
2.17.1
next prev parent reply other threads:[~2018-06-25 11:19 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 ` Alex Bennée [this message]
2018-06-29 11:43 ` [Qemu-devel] [PATCH v1 03/10] build-system: remove per-test GCOV reporting 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é
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=20180625111935.26108-4-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=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).