Skip to content

Commit

Permalink
coverage: Use absolute path when removing paths with lcov
Browse files Browse the repository at this point in the history
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).
  • Loading branch information
tobiasbrunner committed Aug 21, 2017
1 parent 9cf2920 commit 0d11d7b
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Makefile.am
Expand Up @@ -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)" \
Expand Down

0 comments on commit 0d11d7b

Please sign in to comment.