Re: Why is citext/regress failing on hamerkop? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Why is citext/regress failing on hamerkop?
Date
Msg-id 2172456.1715894107@sss.pgh.pa.us
Whole thread Raw
In response to Re: Why is citext/regress failing on hamerkop?  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Why is citext/regress failing on hamerkop?
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> On 2024-05-16 Th 16:18, Tom Lane wrote:
>> Andrew: maybe the buildfarm server could be made to flag
>> animals building exceedingly old commits?  This is the second
>> problem of this sort that I've noticed this month, and you
>> really have to look closely to realize it's happening.

> Yeah, that should be doable. Since we have the git ref these days we 
> should be able to mark it as old, or maybe just reject builds for very 
> old commits (the latter would be easier).

I'd rather have some visible status on the BF dashboard.  Invariably,
with a problem like this, the animal's owner is unaware there's a
problem.  If it's just silently not reporting, then no one else will
notice either, and we effectively lose an animal (despite it still
burning electricity to perform those rejected runs).

            regards, tom lane



pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: commitfest.postgresql.org is no longer fit for purpose
Next
From: "David G. Johnston"
Date:
Subject: Re: commitfest.postgresql.org is no longer fit for purpose