On 17.5.2014 22:35, Tomas Vondra wrote: > 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.
Seems we're still running into this on the CLOBBER_CACHE_ALWAYS animals. The problem is that the git mirror is refreshed only at the very beginning, and while a single branch does not exceed the limit, all the branches do. Could this be solved by keeping a local mirror, without a mirror in the build root? I mean, something like this: git_keep_mirror => 0, scmrepo => '/path/to/local/mirror' And of course a cron script updating the mirror every hour or so. regards Tomas -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers