[Report] 143 regressions on RC_1_34_0 (2007-02-19)

Boost Regression test failures Report time: 2007-02-19T08:17:47Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/is... 143 failures in 14 libraries date_time (4) dynamic_bitset (1) foreach (1) functional/hash (2) graph (3) iostreams (10) iterator (1) math (5) numeric/interval (2) parameter (1) python (73) regex (7) test (25) wave (8) |date_time| testdate_input_facet: msvc-7.1_stlport4 msvc-7.1_stlport4 testdate_input_facet_dll: msvc-7.1_stlport4 msvc-7.1_stlport4 |dynamic_bitset| dyn_bitset_unit_tests2: borland-5.8.2 |foreach| rvalue_const: intel-linux-9.0 |functional/hash| hash_float_test: gcc-cygwin-3.4.4 intel-linux-9.0 |graph| graphviz_test: msvc-7.1_stlport4 msvc-7.1_stlport4 matching_test: msvc-7.1_stlport4 |iostreams| bzip2_test: intel-linux-9.0 msvc-7.1 msvc-8.0 file_descriptor_test: gcc-cygwin-3.4.4 gzip_test: intel-linux-9.0 msvc-7.1 msvc-8.0 zlib_test: intel-linux-9.0 msvc-7.1 msvc-8.0 |iterator| zip_iterator_test: msvc-6.5_stlport4 |math| common_factor_test: msvc-7.1_stlport4 msvc-7.1_stlport4 complex_test: intel-linux-9.0 quaternion_test: intel-linux-9.0 special_functions_test: intel-linux-9.0 |numeric/interval| test_float: msvc-7.1_stlport4 msvc-7.1_stlport4 |parameter| python_test: gcc-cygwin-3.4.4 |python| andreas_beyer: gcc-cygwin-3.4.4 args: gcc-cygwin-3.4.4 auto_ptr: gcc-cygwin-3.4.4 back_reference: gcc-cygwin-3.4.4 bases: gcc-cygwin-3.4.4 intel-linux-9.0 ben_scott1: gcc-cygwin-3.4.4 bienstman1: gcc-cygwin-3.4.4 bienstman2: gcc-cygwin-3.4.4 bienstman3: gcc-cygwin-3.4.4 borrowed: gcc-cygwin-3.4.4 builtin_converters: gcc-cygwin-3.4.4 callbacks: gcc-cygwin-3.4.4 const_argument: gcc-cygwin-3.4.4 crossmod_exception: gcc-cygwin-3.4.4 crossmod_opaque: gcc-cygwin-3.4.4 data_members: gcc-cygwin-3.4.4 defaults: gcc-cygwin-3.4.4 dict: gcc-cygwin-3.4.4 docstring: gcc-cygwin-3.4.4 enum: gcc-cygwin-3.4.4 exception_translator: gcc-cygwin-3.4.4 exec: gcc-cygwin-3.4.4 intel-linux-9.0 extract: gcc-cygwin-3.4.4 implicit: gcc-cygwin-3.4.4 injected: gcc-cygwin-3.4.4 iterator: gcc-cygwin-3.4.4 keywords: gcc-cygwin-3.4.4 list: gcc-cygwin-3.4.4 long: gcc-cygwin-3.4.4 map_indexing_suite: gcc-cygwin-3.4.4 minimal: gcc-cygwin-3.4.4 multi_arg_constructor: gcc-cygwin-3.4.4 nested: gcc-cygwin-3.4.4 numpy: gcc-cygwin-3.4.4 object: gcc-cygwin-3.4.4 object_manager: gcc-cygwin-3.4.4 opaque: gcc-cygwin-3.4.4 operators: gcc-cygwin-3.4.4 pearu1: gcc-cygwin-3.4.4 pickle1: gcc-cygwin-3.4.4 pickle2: gcc-cygwin-3.4.4 pickle3: gcc-cygwin-3.4.4 pickle4: gcc-cygwin-3.4.4 pointee: gcc-cygwin-3.4.4 intel-linux-9.0 pointer_type_id_test: gcc-cygwin-3.4.4 intel-linux-9.0 pointer_vector: gcc-cygwin-3.4.4 polymorphism: gcc-cygwin-3.4.4 polymorphism2: gcc-cygwin-3.4.4 polymorphism2_auto_ptr: gcc-cygwin-3.4.4 properties: gcc-cygwin-3.4.4 raw_ctor: gcc-cygwin-3.4.4 return_arg: gcc-cygwin-3.4.4 select_arg_to_python_test: gcc-cygwin-3.4.4 select_from_python_test: gcc-cygwin-3.4.4 select_holder: gcc-cygwin-3.4.4 shared_ptr: gcc-cygwin-3.4.4 slice: gcc-cygwin-3.4.4 staticmethod: gcc-cygwin-3.4.4 stl_iterator: gcc-cygwin-3.4.4 str: gcc-cygwin-3.4.4 test_pointer_adoption: gcc-cygwin-3.4.4 try: gcc-cygwin-3.4.4 tuple: gcc-cygwin-3.4.4 upcast: gcc-cygwin-3.4.4 intel-linux-9.0 vector_indexing_suite: gcc-cygwin-3.4.4 virtual_functions: gcc-cygwin-3.4.4 voidptr: gcc-cygwin-3.4.4 wrapper_held_type: gcc-cygwin-3.4.4 |regex| regex_regress_dll: gcc-cygwin-3.4.4 regex_regress_threaded: gcc-cygwin-3.4.4 msvc-6.5_stlport4 msvc-7.1_stlport4 msvc-7.1_stlport4 msvc-8.0 test_collate_info: gcc-cygwin-3.4.4 |test| boost_check_equal_str: gcc-mingw-3.4.2 msvc-6.5 msvc-6.5 msvc-6.5_stlport4 errors_handling_test: gcc-mingw-3.4.2 msvc-6.5_stlport4 fixed_mapping_test: gcc-mingw-3.4.2 msvc-6.5_stlport4 ifstream_line_iterator_test: gcc-mingw-3.4.2 msvc-6.5_stlport4 output_test_stream_test: gcc-mingw-3.4.2 msvc-6.5_stlport4 parameterized_test_test: gcc-mingw-3.4.2 msvc-6.5_stlport4 prg_exec_fail3: cw-9.4 result_report_test: gcc-mingw-3.4.2 msvc-6.5_stlport4 test_case_template_test: gcc-mingw-3.4.2 msvc-6.5_stlport4 test_fp_comparisons: gcc-mingw-3.4.2 test_tools_test: gcc-mingw-3.4.2 msvc-6.5 msvc-6.5 msvc-6.5_stlport4 token_iterator_test: gcc-mingw-3.4.2 |wave| test_re2c_lexer: msvc-7.1_stlport4 msvc-7.1_stlport4 test_slex_lexer: msvc-7.1_stlport4 msvc-7.1_stlport4 testwave: msvc-7.1_stlport4 msvc-7.1_stlport4 testwave_dll: msvc-7.1_stlport4 msvc-7.1_stlport4

|wave| test_re2c_lexer: msvc-7.1_stlport4 msvc-7.1_stlport4 test_slex_lexer: msvc-7.1_stlport4 msvc-7.1_stlport4 testwave: msvc-7.1_stlport4 msvc-7.1_stlport4 testwave_dll: msvc-7.1_stlport4 msvc-7.1_stlport4
The logs do not show, what actually went wrong (http://tinyurl.com/2qrq4j). Are the full logs are stored somewhere? Regards Hartmut

Hartmut Kaiser wrote:
|wave| test_re2c_lexer: msvc-7.1_stlport4 msvc-7.1_stlport4 test_slex_lexer: msvc-7.1_stlport4 msvc-7.1_stlport4 testwave: msvc-7.1_stlport4 msvc-7.1_stlport4 testwave_dll: msvc-7.1_stlport4 msvc-7.1_stlport4
The logs do not show, what actually went wrong (http://tinyurl.com/2qrq4j). Are the full logs are stored somewhere?
Yes, see: ftp://fx.meta-comm.com/boost-regression/CVS-RC_1_34_0/logs If that does not help, please ask Roland to run this test by hand and see what's going wrong. - Volodya

Hartmut Kaiser wrote:
|wave| test_re2c_lexer: msvc-7.1_stlport4 msvc-7.1_stlport4 test_slex_lexer: msvc-7.1_stlport4 msvc-7.1_stlport4 testwave: msvc-7.1_stlport4 msvc-7.1_stlport4 testwave_dll: msvc-7.1_stlport4 msvc-7.1_stlport4
The logs do not show, what actually went wrong (http://tinyurl.com/2qrq4j). Are the full logs are stored somewhere?
Hi Hartmut, I've checked the corresponding bjam.log (ftp://fx.meta-comm.com/boost-regression/RC_1_34_0/speedsnail-msvc-dp.zip) and it seems that there the report shows as much as bjam.log has about this compiler failure. -- Misha Bergal MetaCommunications Engineering

Misha Bergal wrote:
|wave| test_re2c_lexer: msvc-7.1_stlport4 msvc-7.1_stlport4 test_slex_lexer: msvc-7.1_stlport4 msvc-7.1_stlport4 testwave: msvc-7.1_stlport4 msvc-7.1_stlport4 testwave_dll: msvc-7.1_stlport4 msvc-7.1_stlport4
The logs do not show, what actually went wrong (http://tinyurl.com/2qrq4j). Are the full logs are stored somewhere?
Hi Hartmut,
I've checked the corresponding bjam.log (ftp://fx.meta-comm.com/boost-regression/RC_1_34_0/speedsnail- msvc-dp.zip) and it seems that there the report shows as much as bjam.log has about this compiler failure.
Thanks! The output (log) was not very helpful, indeed. But then I remembered the VC7.1 problem I had with Wave for a long time now: it fails compiling the file in question when RTTI is on. I committed a fix disabling RTTI for the VC7.1_stlport toolset. Let's see how it goes... Regards Hartmut
--
Misha Bergal MetaCommunications Engineering
_______________________________________________ Boost-Testing mailing list Boost-Testing@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-testing
participants (4)
-
Douglas Gregor
-
Hartmut Kaiser
-
Misha Bergal
-
Vladimir Prus