Re: Execution-time-sensitive timestamp regression tests

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Execution-time-sensitive timestamp regression tests
Date: 2008-05-23 22:47:29
Message-ID: 48374981.5060207@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>
>> And I agree that it's strange we haven't seen it before. Could it be a
>> side-effect from something that happened lately, or should we consider
>> it purely random?
>>
>
> Well, it's possible we have seen it before and ignored it because it
> wasn't reproducible. It was only the coincidence of two buildfarm
> members showing the failure at the same time that drew my attention.
>
> I think Andrew has the ability to grep the buildfarm history to see
> if we've seen this before.
>
> Another possibility is that we did something that improved performance
> to get us below the threshold where this could happen; though I don't
> recall anything very likely.
>
> rega
>

I can't find any other similar failures recently in the buildfarm history.

One data point: the _bat buildfarm members are running on Windows under
VMWare, so their clocks might not be very true.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 2008-05-23 23:15:16 keyword list/ecpg
Previous Message Vishal Mailinglist 2008-05-23 21:34:30 Re: Error while executing pg_dump "invalid memory alloc request size 4294967293"