Horton
Menu

Re: Why is citext/regress failing on hamerkop?

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Thomas Munro <thomas.munro@gmail.com>, buildfarm@sraoss.co.jp, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-05-18T21:31:49Z
Lists: pgsql-hackers 
On 2024-05-16 Th 17:34, Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Small refactoring around ExecCreateTableAs().

  2. Skip citext_utf8 test on Windows.

  3. Fix lost Windows socket EOF events.

  4. Enable routine running of citext's UTF8-specific test cases.

  5. Drops in the CreateProcess calls for Win32 (essentially wrapping up the