diff options
author | Paolo Bonzini <pbonzini@redhat.com> | 2018-10-05 18:17:22 +0200 |
---|---|---|
committer | Thomas Huth <thuth@redhat.com> | 2018-10-16 18:07:23 +0200 |
commit | 26830e9325d05d537dd9a3765437908771d19475 (patch) | |
tree | 24ee85f7a71acabd008bb83cf92ac81e96917c68 /docs | |
parent | 7a6c377f6ba9c86a524965d48849f19a474d5a03 (diff) |
tests: remove gcov-files- variables
Commit 31d2dda ("build-system: remove per-test GCOV reporting", 2018-06-20)
removed users of the variables, since those uses can be replaced by a simple
overall report produced by gcovr. However, the variables were never removed.
Do it now.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
[thuth: Fixed up contextual conflicts with the patch from Eric]
Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'docs')
-rw-r--r-- | docs/devel/testing.rst | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/docs/devel/testing.rst b/docs/devel/testing.rst index 727c4019b5..fcfad87614 100644 --- a/docs/devel/testing.rst +++ b/docs/devel/testing.rst @@ -43,15 +43,13 @@ add a new unit test: 3. Add the test to ``tests/Makefile.include``. First, name the unit test program and add it to ``$(check-unit-y)``; then add a rule to build the - executable. Optionally, you can add a magical variable to support ``gcov``. - For example: + executable. For example: .. code:: check-unit-y += tests/foo-test$(EXESUF) tests/foo-test$(EXESUF): tests/foo-test.o $(test-util-obj-y) ... - gcov-files-foo-test-y = util/foo.c Since unit tests don't require environment variables, the simplest way to debug a unit test failure is often directly invoking it or even running it under |