Horton
Menu

Re: Why is citext/regress failing on hamerkop?

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: TAKATSUKA Haruka <harukat@sraoss.co.jp>
Cc: Thomas Munro <thomas.munro@gmail.com>, Andrew Dunstan <andrew@dunslane.net>, pgsql-hackers <pgsql-hackers@postgresql.org>, buildfarm@sraoss.co.jp
Date: 2024-05-17T16:36:17Z
Lists: pgsql-hackers 
TAKATSUKA Haruka <harukat@sraoss.co.jp> writes:
> I'm a hamerkop maintainer.
> Sorry I have missed the scm error for so long.

> Today I switched scmrepo from git.postgresql.org/git/postgresql.git 
> to github.com/postgres/postgres.git and successfully modernized
> the build target code.

Thanks very much!  I see hamerkop has gone green in HEAD.

It looks like it succeeded in v13 too but failed in v12,
which suggests that the isolationcheck problem is intermittent,
which is not too surprising given our current theory about
what's causing that.

At this point I think we are too close to the 17beta1 release
freeze to mess with it, but I'd support pushing Thomas'
proposed patch after the freeze is over.

			regards, tom lane

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