Re: [Boost-testing] [boost][test]Infinite loop due to recent change?

Subject: Re: [Boost-testing] [boost][test]Infinite loop due to recent change?
From: Belcourt, Kenneth (kbelco_at_[hidden])
Date: 2010-05-18 17:37:37

Hi,

Because this hangs the tester (and the machine becomes unusable), I  
need to comment out this test from the

        libs/test/test/Jamfile.v2

with this change.

Index: libs/test/test/Jamfile.v2
===================================================================
--- libs/test/test/Jamfile.v2	(revision 62090)
+++ libs/test/test/Jamfile.v2	(working copy)
@@ -73,7 +73,7 @@
            [ test-btl-lib run : result_report_test          :  
boost_unit_test_framework : test_files/result_report_test.pattern ]
            [ test-btl-lib run : parameterized_test_test     :  
boost_unit_test_framework ]
            [ test-btl-lib run : test_fp_comparisons         :  
boost_unit_test_framework ]
-          [ test-btl-lib run : test_tools_test             :  
boost_unit_test_framework : test_files/test_tools_test.pattern ]
+          # [ test-btl-lib run : test_tools_test             :  
boost_unit_test_framework : test_files/test_tools_test.pattern ]
            [ test-btl-lib run : test_case_template_test     :  
boost_unit_test_framework ]
            [ test-btl-lib run : custom_exception_test       :  
boost_unit_test_framework/<link>static ]
            [ test-btl-lib run : fixed_mapping_test          :  
boost_unit_test_framework ]

Once the issue is fixed, please re-enable the test.

Committed revision 62091.

-- Noel

On May 18, 2010, at 3:12 PM, Belcourt, Kenneth wrote:

> The Sandia Darwin Intel testers have been stable for some time but a
> recent change seems to have broken the tester.  This test in
> Boost.Test, seems to be the source of the problem (test_tools_test).
>
> brisc: kbelco$ pwd
> /Volumes/Scratch/kbelco/boost/results/boost/bin.v2/libs/test/test/
> test_tools_test.test/intel-darwin-11.0/debug
>
> brisc: kbelco$ more test_tools_test.output
> terminate called after throwing an instance of 'boost::system_error'
> Running 22 test cases...
> terminate called recursively
> terminate called recursively
> terminate called recursively
> terminate called recursively
> [  this message repeated until the test timed out after 5 minutes ]
>
> The test output file size is 260Mb.
>
> -rw-r--r--  1 kbelco  SANDIA\domain users  262252256 May 18 14:13
> test_tools_test.output
>
> This problem causes process_jam_log to loop indefinitely trying to
> digest this enormous output file.  Could Gennadiy or anyone else
> please take a look and see if there's a way to stop the infinite
> looping of "terminate called recursively".
>
> Thanks.
>
> -- Noel
>
>
> _______________________________________________
> Boost-Testing mailing list
> Boost-Testing_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-testing
>