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).

diff --git a/Makefile.am b/Makefile.am
index 47e9e8ce65f2dc4b5b1611e49b8762213b04921d..54b822050299a77b365686ca6fc262d739fdfe77 100644 (file)
--- 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)" \