On 25.04.2009 17:21, Adrian Reber wrote:
On Sat, Apr 25, 2009 at 12:14:22PM +0200, Thorsten Leemhuis wrote:
>> To we want mock to use caching?
> I'd say we want a root_cache, as it seems to speed things up a bit.
>
> I guess we could/should disable the yum_cache, as all builders have
> nearby mirrors. Or we enable it and stop maintaining those nearby
> mirrors. Or we chose depending on builder.
>
> I'm not sure if ccache is worth the trouble. I tend to say "no".
>
> Does anyone know if Fedora handles those different caching strategies on
> its builders?
Nobody?
>> Because then I have to increase the disk space (which is no
problem).
> FYI, /var/cache/mock/ grew up to 13G on j-rod's builder over the past
> few days (which is not building EL). But I guess it'll grow even more
> over time.
Then I will add 20G under /var/cache/mock/ and restart the builder. Does
that sound right?
Wait a bit; I disabled package-caching and ccache on your builder for
now, so I guess we won't run into space problems soon again.
And I really would like to discuss the proper way for building and
caching on our builders. Right now we have a local mirror on each
system; those sometimes are out of date or broken, resulting in problems
like the one with the ppc64 builder earlier today, which makes life
difficult for everyone.
Maybe we should just use MirrorManger where possible and rely on the
package cache from mock? That might solve above problems, but create
others...
CU
knurd