Re: coverage.postgresql.org not being refreshed

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Peter Geoghegan <pg(at)bowt(dot)ie>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL www <pgsql-www(at)postgresql(dot)org>
Subject: Re: coverage.postgresql.org not being refreshed
Date: 2021-01-23 18:48:53
Message-ID: CABUevEwx=9zP1ADsY+zwk1euT59u+FczsepSemKB+HzotLweqQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Sat, Jan 23, 2021 at 6:51 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>
> coverage.postgresql.org reports that its "current" coverage report is
> from 2021-01-11 19:06:43. I imagine that the backend infrastructure
> that runs lcov is having issues.

It's indeed failing, and it seems we don't have any monitoring on it :/

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

And that's what's been failing. And it is also failing for me locally.

So it seems we have a test that's failing on debian at least. But we
never run this on the buildfarm anywhere?

Looking at the git log of that directory, I'm guessing it's related to
some of the error message changes from Tom.

(And I've now added monitoring)

--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Tom Lane 2021-01-23 19:45:05 Re: coverage.postgresql.org not being refreshed
Previous Message Peter Geoghegan 2021-01-23 17:51:36 coverage.postgresql.org not being refreshed