| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Bogus reports from coverage.postgresql.org |
| Date: | 2018-03-14 20:55:19 |
| Message-ID: | c8608309-b7b6-54c7-76b1-09ac67163433@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On 3/14/18 12:31, Tom Lane wrote:
> Recommended procedure when capturing data for a test case:
>
> 1. create baseline coverage data file
> # lcov -c -i -d appdir -o app_base.info
>
> 2. perform test
> # appdir/test
>
> 3. create test coverage data file
> # lcov -c -d appdir -o app_test.info
>
> 4. combine baseline and test coverage data
> # lcov -a app_base.info -a app_test.info -o
> app_total.info
>
> Our process swaps steps 1 and 2.
That doesn't matter because 1 and 3 are independent of another. The
pipeline is
1 ------\
|--> 4
2 -> 3 -/
Our makefiles are set up in exactly this way and may run 1 and 3 in
parallel.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-03-15 16:00:32 | Re: Bogus reports from coverage.postgresql.org |
| Previous Message | Tom Lane | 2018-03-14 20:45:04 | Re: Bogus reports from coverage.postgresql.org |