hamerkop is stuck

Noah Misch <noah@leadboat.com>

From: Noah Misch <noah@leadboat.com>

To: buildfarm@sraoss.co.jp

Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2015-01-16T08:25:00Z

Lists: pgsql-hackers

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

Commits

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

Have config_sspi_auth() permit IPv6 localhost connections.
- 8d9cb0bc4834 9.5.0 cited
Lock down regression testing temporary clusters on Windows.
- f6dc6dd5ba54 9.5.0 cited
Use a separate temporary directory for the Unix-domain socket
- f545d233ebce 9.5.0 cited
Secure Unix-domain sockets of "make check" temporary clusters.
- be76a6d39e28 9.5.0 cited