From 0d11d7b1109973e72beee40649e1ef3e6377665d Mon Sep 17 00:00:00 2001 From: Tobias Brunner Date: Mon, 21 Aug 2017 11:08:59 +0200 Subject: [PATCH] coverage: Use absolute path when removing paths with lcov There is a bug in some versions of lcov that causes it to fail writing to files via relative paths after it issued warnings (e.g. due to negative counts in the tracefile). --- Makefile.am | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile.am b/Makefile.am index 47e9e8ce6..54b822050 100644 --- a/Makefile.am +++ b/Makefile.am @@ -59,7 +59,7 @@ cov-report: lcov -c -o $(top_builddir)/coverage/coverage.info -d $(top_builddir) \ --rc lcov_branch_coverage=1 lcov -r $(top_builddir)/coverage/coverage.info '*/tests/*' '*/suites/*' '/usr*' \ - -o $(top_builddir)/coverage/coverage.cleaned.info \ + -o $(abs_top_builddir)/coverage/coverage.cleaned.info \ --rc lcov_branch_coverage=1 genhtml --num-spaces 4 --legend --branch-coverage --ignore-errors source \ -t "$(PACKAGE_STRING)" \