| From: | Robert Creager <robert(at)logicalchaos(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: Fwd: PGBuildfarm member colugos Branch HEAD Status changed from OK to StartDb-C:3 failure |
| Date: | 2010-05-20 18:03:13 |
| Message-ID: | 7D076EE6-837D-430E-AF34-4A2BB2862574@logicalchaos.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On May 20, 2010, at 11:54 AM, Tom Lane wrote:
> Robert Creager <rsc(at)logicalchaos(dot)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 that correlates 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-05-20 18:12:13 | Re: Fwd: PGBuildfarm member colugos Branch HEAD Status changed from OK to StartDb-C:3 failure |
| Previous Message | Josh Berkus | 2010-05-20 17:58:17 | Re: Clarifications of licences on pgfoundry |