| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, buildfarm(at)sraoss(dot)co(dot)jp, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Why is citext/regress failing on hamerkop? |
| Date: | 2024-05-16 21:15:07 |
| Message-ID: | 2172456.1715894107@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-05-16 21:15:39 | Re: commitfest.postgresql.org is no longer fit for purpose |
| Previous Message | Joe Conway | 2024-05-16 21:10:23 | Re: commitfest.postgresql.org is no longer fit for purpose |