Alvaro Herrera writes:
> Excerpts from Tom Lane's message of mar sep 20 21:30:42 -0300 2011:
>> Could we please fix those tests to not have such
>> fragile timing assumptions?
> The fix has now been installed for two weeks and no new failure has
> occured. The only failure in the IsolationCheck
Excerpts from Tom Lane's message of mar sep 20 21:30:42 -0300 2011:
>
> The buildfarm is still showing isolation test failures more days than
> not, eg
> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=pika&dt=2011-09-17%2012%3A43%3A11
> and I've personally seen such failures when testing
Alvaro Herrera writes:
> The main problem I have is that I haven't found a way to reproduce the
> problems in my machine.
Try -DCLOBBER_CACHE_ALWAYS.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscrip
Excerpts from Kevin Grittner's message of mar sep 20 22:51:39 -0300 2011:
> If I remember right, Alvaro chose these timings to balance run time
> against chance of failure. Unless we want to remove these deadlock
> handling tests or ignore failures (which both seem like bad ideas to
> me), I thi
Tom Lane wrote:
> The buildfarm is still showing isolation test failures more days
> than not, eg
>
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=pika&dt=2011-09-17%2012%3A43%3A11
> and I've personally seen such failures when testing with
> CLOBBER_CACHE_ALWAYS. Could we please fix tho
The buildfarm is still showing isolation test failures more days than
not, eg
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=pika&dt=2011-09-17%2012%3A43%3A11
and I've personally seen such failures when testing with
CLOBBER_CACHE_ALWAYS. Could we please fix those tests to not have such
fra
