From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: coverage analysis improvements |
Date: | 2017-08-21 05:23:02 |
Message-ID: | CAB7nPqSgP_DBEUF_SBBsfYmHdKkJHrVdzcjACz_JAi4xZH411Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Aug 11, 2017 at 1:05 PM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> Here is a patch series with some significant reworking and adjusting of
> how the coverage analysis tools are run. The result should be that the
> "make coverage" runs are faster and more robust, the results are more
> accurate, and the code is simpler. Please see the individual patches
> for details.
>
> I have replaced "make coverage-html" with "make coverage" (but kept the
> previous name for compatibility), since the old meaning of the latter
> has gone away and was never very useful. Other than that, the usage of
> everything stays the same.
>
> I will add it to the commit fest. Testing with different versions of
> tools would be especially valuable.
Patch 0001 fails to apply as of c629324. Which versions of lcov and
gcov did you use for your tests?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2017-08-21 05:45:43 | Re: Proposal: global index |
Previous Message | Michael Paquier | 2017-08-21 05:11:44 | Re: assorted code cleanup |