| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | 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 14:31:31 |
| Message-ID: | 5ca841a1-1506-fda0-6428-08e31c38c3f2@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On 3/13/18 13:45, Tom Lane wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
>> Running gcov on the box itself in the source dir shows the same results
>> which you got:
>
> Oh really!
>
>> Which seems to indicate that this actually is some kind of lcov bug.
>
> Yeah. I'd written that off as too low-probability to worry about,
> but maybe not. I'll poke further. Peter, which lcov did you test?
lcov: LCOV version 1.13
The one that comes with Debian stable, presumably the same that is
running on coverage.p.o.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-03-14 15:32:58 | Re: Bogus reports from coverage.postgresql.org |
| Previous Message | Oleg Bartunov | 2018-03-14 10:48:21 | Main page of wiki.postgresql.org |