| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL www <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: coverage.postgresql.org not being refreshed |
| Date: | 2021-01-23 23:12:49 |
| Message-ID: | CABUevExib9RBVE=tCWJt+FSqpjBRrji8h2uEMq9FNO-Emd2j+A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Sat, Jan 23, 2021 at 8:45 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> > All runs since the 11th have failed with a dead regression test:
> > test connect/test1 ... stderr FAILED 202 ms
>
> > I notice that the coverage scripts explicitly run:
> > make -C src/interfaces/ecpg/test checktcp
>
> Ugh, no I never run that test either. Will fix.
Thanks! You missed the cron by a couple of minutes, but it recovered
on the next run.
Is there a particular reason we don't run it on the buildfarm, at
least on some animals? Seems like that would be a much better way of
finding these problems...
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-01-23 23:23:07 | Re: coverage.postgresql.org not being refreshed |
| Previous Message | Peter Geoghegan | 2021-01-23 21:33:58 | Re: coverage.postgresql.org not being refreshed |