Boost Testing :
Subject: Re: [Boost-testing] [EXTERNAL] Re: GCC runners failing (and stopping)
From: Belcourt, Kenneth (kbelco_at_[hidden])
Date: 2014-07-02 22:42:40
On Jul 2, 2014, at 8:37 PM, "Belcourt, Kenneth" <kbelco_at_[hidden]>
> On Jul 2, 2014, at 8:18 PM, Tom Kent <lists_at_[hidden]>
>> On Wed, Jul 2, 2014 at 8:55 PM, Tom Kent <lists_at_[hidden]> wrote:
>> Both of my linux-development runners (teeks99-03, teeks99-04) are locking up during their runs.
> If I run a debug built PJL by hand:
> /scratch/boost_testing/boost_root/tools/regression/build/bin/gcc-4.4.6/debug/process_jam_log --echo --boost-root `pwd` < results/bjam.log
> It does indeed hang at this test:
> 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).
-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.