Re: [Boost-testing] [EXTERNAL] Re: GCC runners failing (and stopping)

Subject: Re: [Boost-testing] [EXTERNAL] Re: GCC runners failing (and stopping)
From: John Maddock (boost.regex_at_[hidden])
Date: 2014-07-03 04:25:41

>> line 66106: testing.capture-output /scratch/boost_testing/results/boost/bin.v2/libs/multiprecision/test/test_cpp_bin_float_io_1.test/gcc-4.8.2/release/test_cpp_bin_float_io_1.run
>> 	line_start: testing.capture-output
>> 	target_directory( "testing.capture-output /scratch/boost_testing/results/boost/bin.v2/libs/multiprecision/test/test_cpp_bin_float_io_1.test/gcc-4.8.2/release/test_cpp_bin_float_io_1.run") -> "results/boost/bin.v2/libs/multiprecision/test/test_cpp_bin_float_io_1.test/gcc-4.8.2/release"
>>
>> Not sure why.  So yes, it does appear that there is a problem.
>
> So the problem seems to be this output file is quite large (perhaps John can help prune this down to reasonable size).
>
> results/boost/bin.v2/libs/multiprecision/test/test_cpp_bin_float_io_1.test/gcc-4.8.2/release
>
> -rw-r--r-- 1 kbelco kbelco 102842264 Jul  2 19:29 test_cpp_bin_float_io_1.output
>
> I'd guess PJL is choking trying to absorb this 100Mb test result.

It shouldn't be generating that much output (or any output for that 
matter).  I assume this is in develop?  I've managed to completely mess 
up my local Git repro (don't ask!), but as soon as I can get a fresh one 
downloaded I'll investigate.

Thanks for the heads up, John.