| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| 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-11 20:01:26 |
| Message-ID: | 13148.1520798486@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> I tried it on Debian stable with gcc 6.3.0 and couldn't reproduce it.
> cc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
Oh ... *that's* interesting. Are we sure this is the version in use
on coverage.postgresql.org?
Also, I just finished searching in vain for any plausibly-matching
bug at https://gcc.gnu.org/bugzilla/. I did find a few reports
suggesting that gcov could misbehave with nondefault build options
such as LTO. And "gcov -a" has also had issues. So maybe we ought
to have a look at exactly what coverage.postgresql.org's build
recipe is.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-03-11 20:05:30 | Re: Bogus reports from coverage.postgresql.org |
| Previous Message | Magnus Hagander | 2018-03-11 19:56:45 | Re: Bogus reports from coverage.postgresql.org |