Horton
Menu

Re: hamerkop is stuck

TAKATSUKA Haruka <harukat@sraoss.co.jp>

View thread
From: TAKATSUKA Haruka <harukat@sraoss.co.jp>
To: Noah Misch <noah@leadboat.com>
Cc: buildfarm@sraoss.co.jp, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2015-01-19T01:44:37Z
Lists: pgsql-hackers 
Hello.

Sorry about giving corrupted reports.
We examine what it is caused by now.

regards,

---
 TAKATSUKA Haruka  harukat@sraoss.co.jp
 SRA OSS, Inc.  http://www.sraoss.co.jp


On Fri, 16 Jan 2015 03:25:00 -0500
Noah Misch <noah@leadboat.com> wrote:

> Buildfarm member hamerkop stopped reporting in after commit f6dc6dd.  After
> commit 8d9cb0b, it resumed reporting in for 9.3 and earlier branches.  It is
> still silent for HEAD and REL9_4_STABLE.  It may have stale processes or stale
> lock files requiring manual cleanup.  Would you check it?
> 
> Thanks,
> nm
> 
> 
> -- 
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

Commits

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

  1. Have config_sspi_auth() permit IPv6 localhost connections.

  2. Lock down regression testing temporary clusters on Windows.

  3. Use a separate temporary directory for the Unix-domain socket

  4. Secure Unix-domain sockets of "make check" temporary clusters.