"Alceu R. de Freitas Jr." via cpan-testers-discuss
<cpan-testers-discuss@perl.org> writes:
> Hello folks,
> Is there any kind of standards/recommendations about CPAN build_dir
> configuration regarding disk space available?
Limits on my smokers are:
- the partition containing the build dir should have at least 2GB disk
space available, on some tight systems only 1GB
- the partition containing TMPDIR should have at least 50MB disk space
available
The disk free check is done before running tests on a batch of
distributions, for different sizes of "batch", so in worst case disks
still may fill up.
Usually the only CPAN distributions which come near these limits are
Alien::* modules. Recently I had to completely disable one of these
(Alien-gdal), because building took up to 6GB.
> In order to speed things up on OpenBSD, I'm using a MFS filesystem which is
> allocated exclusively for build_dir. Of course, since it RAM, I don't have
> much space for it (~1G).
> Even with an aggressive control of cache ("clean_cache_after => 50" for
> CPAN::Reporter::Smoker), in some situations I'm still getting all build_dir
> storage consumed, which of course cause reports to fail.
> I was able to identify distributions that uses a lot of storage during it's
> build... not sure if they should look for a different filesystem (/tmp ?) in
> cases like that.
/tmp may also be on a memory file system, or have another limit.
> Another things is how to identify those distributions... is there any way to
> measure this?
Just measure occupied disk space before and after? Of course, this does
not work if you test distributions in parallel, or in case of large
dependency trees it's not easy to identify the one distribution causing
the problem.
In any way you should probably check the reports for strings like "No
space left on device" and deal with these reports manually (i.e. choose
to not send them).
Regards,
Slaven
--
Slaven Rezic - slaven <at> rezic <dot> de
Berlin Perl Mongers - http://berlin.pm.org
