On 08/14/2011 05:09 PM, Maarten Brock wrote:
> Hi Borut,
>>> Dear DCF maintainers,
>> probably me...
> Yes, but also the owners of the DCF machines as it is their harddisk
> space I'm asking.
>>> Would it please be possible to keep the build results of the latest
>>> snapshot around? Currently they are removed at the end of the snapshot
>>> build/test. This means the disk space would be permanently allocated
>>> instead of only during build/test. I hope this is no big deal for you.
>> Problem is that the build directories are deleted at the beginning of
>> each build script invocation and the build script is invoked two times:
>> once for complete build and once for upload. So the upload deletes the
>> build results.
> Can that be changed to only once? Does upload need to call the build
Done: a Quick & Dirty hack in the build script disables deletion of
build dirs in case of do_upload.
>> Additional problem are multi host / cross compilation builds: each build
>> removes results of the previous one. Such case are x86_64, x86 and mingw
>> builds, which are all (currently) executed at cf-x86, one after the other.
> Can each build be created in a separate directory? Do the DCF servers
> have enough space for that?
Good idea, I'll take a look. The space should not be a problem: from now
on x86 build are be done on derna (mingw32 builds too, but currently I
have some problems with regression testing), so max. 2 builds will be
done on each machine.