Be more thorough about cleaning out gcov litter.

At least on my machine, a run with code coverage enabled produces some
".gcov" files whose names begin with ".".  "rm -f *.gcov" fails to match
those, so they don't get cleaned up by "make clean".  Fix it.
This commit is contained in:
Tom Lane 2017-08-11 17:39:27 -04:00
parent 3c8de95979
commit d6ecad812f
1 changed files with 2 additions and 2 deletions

View File

@ -878,7 +878,7 @@ ifeq ($(enable_coverage), yes)
gcda_files := $(wildcard *.gcda)
lcov.info: $(gcda_files)
rm -f *.gcov
rm -f *.gcov .*.gcov
$(if $^,$(LCOV) -d . -c -o $@ $(LCOVFLAGS) --gcov-tool $(GCOV))
%.c.gcov: %.gcda | lcov.info
@ -899,7 +899,7 @@ clean distclean maintainer-clean: clean-coverage
.PHONY: clean-coverage
clean-coverage:
rm -rf coverage
rm -f *.gcda *.gcno lcov.info *.gcov *.gcov.out
rm -f *.gcda *.gcno lcov.info *.gcov .*.gcov *.gcov.out
# User-callable target to reset counts between test runs