| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, 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 16:12:48 |
| Message-ID: | 20180314161248.ai7mmw4wlgnxxdtt@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Alvaro Herrera wrote:
> In the coverage.pg.org box, we have:
>
> $ cat .lcovrc
> lcov_branch_coverage = 1
>
> I'm going to do a test run with that disabled and see what happens.
So the counters for the "bogus" line are reported as zero now, but we
lost branch-based numbers. I suppose we can live with that, if we don't
want to try and track down the bug. I suppose you could try to
reproduce it locally with that setting.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-03-14 16:15:17 | Re: Bogus reports from coverage.postgresql.org |
| Previous Message | Alvaro Herrera | 2018-03-14 15:43:52 | Re: Bogus reports from coverage.postgresql.org |