Re: Fwd: PGBuildfarm member colugos Branch HEAD Status changed from OK to StartDb-C:3 failure - Mailing list pgsql-hackers

From Robert Creager
Subject Re: Fwd: PGBuildfarm member colugos Branch HEAD Status changed from OK to StartDb-C:3 failure
Date
Msg-id 7D076EE6-837D-430E-AF34-4A2BB2862574@logicalchaos.org
Whole thread Raw
In response to Re: Fwd: PGBuildfarm member colugos Branch HEAD Status changed from OK to StartDb-C:3 failure  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On May 20, 2010, at 11:54 AM, Tom Lane wrote:

> Robert Creager <rsc@logicalchaos.org> writes:
>> If anyone is interested, I think this failure was accompanied by the following:
>> [ apparent PANIC in UpdateControlFile ]
>
> Hmm, do you have the panic message in the postmaster log?  So far as I
> can tell, the postmaster log isn't captured anywhere in the buildfarm
> report of this event.  (Which seems like a buildfarm bug.)

'Course not.

>
> Given that polecat has already run a couple of later buildfarm
> iterations, I'm not too hopeful that you do have that log file.
> Was there any special environment here, like running out of disk space?

Not that I'm aware of.  I did empty trash sometime yesterday after noticing I was around 1Gb of free disk.  Not sure if
thatcorrelates or not.  Maybe on failure buildfarm should could disk usage of the disk it's on and add that to the
report?

I've updated my OSX clients to keep error builds.

Later,
Rob

pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Clarifications of licences on pgfoundry
Next
From: "Andrew Dunstan"
Date:
Subject: Re: Clarifications of licences on pgfoundry