Re: buildfarm instance bichir stuck

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Robins Tharakan <tharakan(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: buildfarm instance bichir stuck
Date: 2021-04-07 20:02:38
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)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
I've had issues of those sorts before ...

regards, tom lane

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2021-04-07 20:13:21 Re: multi-install PostgresNode fails with older postgres versions
Previous Message Tom Lane 2021-04-07 19:57:31 Re: psql \df choose functions by their arguments