On Thu, 2011-05-05 at 10:12 -0600, Tim Flink wrote:
On 05/05/2011 07:24 AM, James Laska wrote:
> Jobs with *obscenely* large logs ...
> 1.2G /usr/share/autotest/results/91523-autotest
> 3.0G /usr/share/autotest/results/91524-autotest
> 1.9G /usr/share/autotest/results/91550-autotest
> 1.5G /usr/share/autotest/results/91604-autotest
> 2.0G /usr/share/autotest/results/91605-autotest
> 967M /usr/share/autotest/results/91549-autotest
> 933M /usr/share/autotest/results/91635-autotest
> 685M /usr/share/autotest/results/91634-autotest
> 536M /usr/share/autotest/results/92318-autotest
> 200M /usr/share/autotest/results/92317-autotest
These are all depcheck F15 updates-testing (both i386 and x86_64)
> 252M /usr/share/autotest/results/91705-autotest
This one is compose_tree F14 which is storing the generated boot.iso
(~250M) in the log directory (compose_tree/results/boot.iso). Do we
really want to be doing that?
No, I'll update that test ... I just haven't figured out how I'd like to
adjust it yet.
Thanks,
James