Re: buildfarm instance bichir stuck - Mailing list pgsql-hackers

From Tom Lane
Subject Re: buildfarm instance bichir stuck
Date
Msg-id 1645428.1617825758@sss.pgh.pa.us
Whole thread Raw
In response to Re: buildfarm instance bichir stuck  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: buildfarm instance bichir stuck  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> On 4/7/21 1:07 PM, Tom Lane wrote:
>> I do use it on some of my flakier dinosaurs, and I've noticed that
>> when it does kick in, the buildfarm run just stops dead and no report
>> is sent to the BF server.  That has advantages in not cluttering the
>> BF status with run-failed-because-of-$weird_problem issues, but it
>> doesn't help from the standpoint of noticing when your animal is stuck.
>> Maybe it'd be better to change that behavior.

> Yeah, I'll have a look. It's not simple for a bunch of reasons.

On further thought, that doesn't seem like the place to fix it.
I'd rather be able to ask the buildfarm server to send me nagmail
if my animal hasn't sent a report in N days (where N had better
be owner-configurable).  This would catch not only animal-is-hung,
but also other classes of problems like whole-machine-is-hung or
you-broke-your-firewall-configuration-so-it-cant-contact-the-server.
I've had issues of those sorts before ...

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: psql \df choose functions by their arguments
Next
From: Andrew Dunstan
Date:
Subject: Re: multi-install PostgresNode fails with older postgres versions