Re: Why is citext/regress failing on hamerkop?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-18 21:31:49
Message-ID: d12434a0-cf08-475d-875e-17c3a3ef1020@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2024-05-16 Th 17:34, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> On 2024-05-16 Th 17:15, Tom Lane wrote:
>>> 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).
>> Fair enough. That will mean some database changes and other stuff, so it
>> will take a bit longer.
> Sure, I don't think it's urgent.

I've pushed a small change, that should just mark with an asterisk any
gitref that is more than 2 days older than the tip of the branch at the
time of reporting.

cheers

andrew

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2024-05-18 21:35:04 Re: Ignore Visual Studio's Temp Files While Working with PG on Windows
Previous Message Josef Šimánek 2024-05-18 21:31:07 Re: Ignore Visual Studio's Temp Files While Working with PG on Windows