pgsql: Run only top-level recursive lcov

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Run only top-level recursive lcov
Date: 2017-09-28 12:54:08
Message-ID: E1dxYKO-0006JS-8h@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Run only top-level recursive lcov

This is the way lcov was intended to be used. It is much faster and
more robust and makes the makefiles simpler than running it in each
subdirectory.

The previous coding ran gcov before lcov, but that is useless because
lcov/geninfo call gcov internally and use that information. Moreover,
this led to complications and failures during parallel make. This
separates the two targets: You either use "make coverage" to get
textual output from gcov or "make coverage-html" to get an HTML report
via lcov. (Using both is still problematic because they write the same
output files.)

Reviewed-by: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/504923a0ed5c75775196c8ed0cd59b15d55cd39b

Modified Files
--------------
.gitignore | 1 +
doc/src/sgml/regress.sgml | 13 +++++++++++++
src/Makefile.global.in | 28 ++++++++++++++++------------
3 files changed, 30 insertions(+), 12 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2017-09-28 14:47:53 pgsql: Fix freezing of a dead HOT-updated tuple
Previous Message Tom Lane 2017-09-28 12:21:37 Re: pgsql: Add test for postmaster crash restarts.