Robins Tharakan <thara...@gmail.com> writes:
> Not sure if many agree but 2 things stood out here:
> 1) Buildfarm never got the message that a commit broke an instance. Ideally
> I'd have expected buildfarm to have an optimistic timeout that could have
> helped - for e.g. right now, the CREATE DATABASE is still stuck since 18
> hrs.
As far as that goes, you can set wait_timeout in the animal's config
to something comfortably more than the longest run time you expect.
It doesn't default to enabled though, possibly because picking a
one-size-fits-all value would be impossible.
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.
(I can also attest from personal experience that what had been a
comfortable amount of slop when you picked it tends to become less
so over time. Consider yourself warned.)
regards, tom lane
