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-17 20:35:29 |
Message-ID: | 5377C811.9060702@fuzzy.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 17.5.2014 19:58, Andrew Dunstan wrote:
>
> On 05/15/2014 07:47 PM, Tomas Vondra wrote:
>> 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).
>
>
>
> I have made a change that omits the snapshot sanity check for
> CLOBBER_CACHE_RECURSIVELY cases, but keeps it for all others. See
> <https://github.com/PGBuildFarm/server-code/commit/abd946918279b7683056a4fc3156415ef31a4675>
OK, thanks. Seems reasonable.
Tomas
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2014-05-17 20:46:39 | Re: btree_gist macaddr valgrind woes |
Previous Message | Andres Freund | 2014-05-17 20:34:04 | Re: %d in log_line_prefix doesn't work for bg/autovacuum workers |