Re: buildfarm animals and 'snapshot too old'

From: Tomas Vondra <tv(at)fuzzy(dot)cz>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: buildfarm animals and 'snapshot too old'
Date: 2014-05-15 23:47:16
Message-ID: 53755204.6070001@fuzzy.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 15.5.2014 22:07, Andrew Dunstan wrote:
>
> Yes, I've seen that. Frankly, a test that takes something like 500
> hours is a bit crazy.

Maybe. It certainly is not a test people will use during development.
But if it can detect some hard-to-find errors in the code, that might
possibly lead to serious problems, then +1 from me to run them at least
on one animal. 500 hours is ~3 weeks, which is not that bad IMHO.

Also, once you know where it fails the developer can run just that
single test (which might take minutes/hours, but not days).

> If we really want to run this in the buildfarm we should probably
> try to create a massively cut down test schedule for use in this
> case.

If we can run cut this down in a meaningful way (i.e. without
sacrificing most of the benefits) then sure - let's do that. But I think
that's what CLOBBER_CACHE_ALWAYS is about.

regards
Tomas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Blagoj Petrushev 2014-05-16 00:06:06 Trigger concurrent execution
Previous Message Tomas Vondra 2014-05-15 23:36:17 Re: buildfarm animals and 'snapshot too old'