Re: PG vs LLVM 12 on seawasp, next round

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PG vs LLVM 12 on seawasp, next round
Date: 2021-02-15 19:50:34
Message-ID: ca1a8697-ecdf-7fa5-d122-87349f04c7fd@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 1/24/21 11:06 PM, Tom Lane wrote:
> Noah Misch <noah(at)leadboat(dot)com> writes:
>> On Mon, Jan 18, 2021 at 09:29:53PM +0100, Fabien COELHO wrote:
>>> ... Last two months were a
>>> little overworked for me so I let slip quite a few things. If you want to
>>> disable the animal as Tom suggests, do as you want.
>> Perhaps he was suggesting that you (buildfarm owner) disable the cron job that
>> initiates new runs. That's what I do when one of my animals needs my
>> intervention.
> Indeed. I'm not sure there even is a provision to block an animal on the
> buildfarm-server side. If there is, you'd have to request that it be
> manually undone after you get around to fixing the animal. Frankly,
> if I were the BF admin, I would be in about as much hurry to do that
> as you've been to fix it.
>
>

It's actually very easy, but it's something I usually reserve for people
who are very unresponsive to emails. As noted, disabling the crontab
entry on the client side is a preferable solution.

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bossart, Nathan 2021-02-15 20:19:40 Re: partial heap only tuples
Previous Message Fabien COELHO 2021-02-15 19:41:39 Re: PG vs LLVM 12 on seawasp, next round