| From: | "Tomas Vondra" <tv(at)fuzzy(dot)cz> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | buildfarm animals and 'snapshot too old' |
| Date: | 2014-05-15 16:43:35 |
| Message-ID: | 9c89469383a1cadb3266f2ea87cde2cf.squirrel@sq.gransy.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi all,
today I got a few of errors like these (this one is from last week, though):
Status Line: 493 snapshot too old: Wed May 7 04:36:57 2014 GMT
Content:
snapshot to old: Wed May 7 04:36:57 2014 GMT
on the new buildfarm animals. I believe it was my mistake (incorrectly
configured local git mirror), but it got me thinking about how this will
behave with the animals running CLOBBER_CACHE_RECURSIVELY.
If I understand the Perl code correctly, it does this:
(1) update the repository
(2) run the tests
(3) check that the snapshot is not older than 24 hours (pgstatus.pl:188)
(4) fail if older
Now, imagine that the test runs for days/weeks. This pretty much means
it's wasted, because the results will be thrown away anyway, no?
regards
Tomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-05-15 16:57:35 | Logical replication woes |
| Previous Message | Tom Lane | 2014-05-15 16:39:03 | Re: Unportability of setvbuf() |