| From: | Robert Creager <robert(at)logicalchaos(dot)org> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: buildfarm logging versus embedded nulls |
| Date: | 2010-03-12 16:20:06 |
| Message-ID: | 50FB6B5A-CFD4-4730-84C9-F39EADD1366F@logicalchaos.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mar 11, 2010, at 6:00 PM, Andrew Dunstan wrote:
>
>
> Tom Lane wrote:
>> I was looking at this recent nonrepeatable buildfarm failure:
>> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=polecat&dt=2010-03-11%2021:45:10
>> which has several instances of the known "pgstat wait timeout" problem
>> during the parallel regression tests.
You've got me trained well now. I'm now looking at my build machine failures. Wasn't sure what to do about that one, since no relevant files changed.
Is there any value in setting "keep_error_builds => 0,"? I know Andrew was able to get the complete log file.
Cheers,
Rob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2010-03-12 16:34:21 | Re: buildfarm logging versus embedded nulls |
| Previous Message | Tom Lane | 2010-03-12 15:56:41 | Re: buildfarm logging versus embedded nulls |