Re: coverage.postgresql.org not being refreshed

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Peter Geoghegan <pg(at)bowt(dot)ie>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL www <pgsql-www(at)postgresql(dot)org>
Subject: Re: coverage.postgresql.org not being refreshed
Date: 2021-01-24 01:24:38
Message-ID: 1505399.1611451478@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> Is there a convenient way to compare two coverage runs?

Hmm ... diff'ing the html output is really painful, but it
looks like using checktcp instead of check causes 48 lines
in ecpg to change from not-covered to covered.

$ grep -r lineNoCov coverage.std/src/interfaces/ecpg | wc
12555 120279 2212944
$ grep -r lineNoCov coverage.tcp/src/interfaces/ecpg | wc
12507 119723 2153410

regards, tom lane

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Tom Lane 2021-01-24 02:01:22 Re: coverage.postgresql.org not being refreshed
Previous Message Alvaro Herrera 2021-01-24 00:45:44 Re: coverage.postgresql.org not being refreshed