Re: Why is citext/regress failing on hamerkop?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: TAKATSUKA Haruka <harukat(at)sraoss(dot)co(dot)jp>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, buildfarm(at)sraoss(dot)co(dot)jp
Subject: Re: Why is citext/regress failing on hamerkop?
Date: 2024-05-17 16:36:17
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

TAKATSUKA Haruka <harukat(at)sraoss(dot)co(dot)jp> writes:
> I'm a hamerkop maintainer.
> Sorry I have missed the scm error for so long.

> Today I switched scmrepo from
> to 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2024-05-17 16:44:52 problems with "Shared Memory and Semaphores" section of docs
Previous Message Tom Lane 2024-05-17 16:29:47 Re: is no longer fit for purpose