Boost regression notification (2005-06-30)
Boost regression test failures ------------------------------ Report time: 2005-06-30T05:35:19Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. random preprocessor io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues.... 353 failures in 14 libraries: bind (1) io (2) iterator (2) numeric/ublas (21) preprocessor (1) program_options (12) python (56) random (3) regex (2) serialization (236) spirit (5) test (6) thread (2) wave (4) |bind| mem_fn_eq_test: intel-win32-8_1 |io| ios_state_unit_test: intel-win32-8_1 intel-win32-8_1 |iterator| filter_iterator_test: intel-win32-8_1 lvalue_concept_fail: intel-win32-8_1 |numeric/ublas| concepts: cw-9_4 cw-9_4 cw-9_5-darwin test1: cw-9_4 cw-9_4 cw-9_5-darwin test2: cw-9_4 cw-9_4 cw-9_5-darwin test3: cw-9_4 cw-9_4 cw-9_5-darwin test4: cw-9_4 cw-9_4 cw-9_5-darwin test5: cw-9_4 cw-9_4 cw-9_5-darwin test6: cw-9_4 cw-9_4 cw-9_5-darwin |preprocessor| seq: cw-8_3 |program_options| cmdline_test: vc-7_0 cmdline_test_dll: mingw-3_4_2 vc-7_0 parsers_test: vc-7_0 parsers_test_dll: vc-7_0 positional_options_test_dll: mingw-3_4_2 unicode_test: vc-7_0 unicode_test_dll: cw-9_5-darwin gcc-3_3-darwin vc-7_0 variable_map_test: vc-7_0 variable_map_test_dll: vc-7_0 |python| andreas_beyer: intel-win32-8_1 args: intel-win32-8_1 auto_ptr: intel-win32-8_1 back_reference: intel-win32-8_1 ben_scott1: intel-win32-8_1 bienstman1: intel-win32-8_1 bienstman2: intel-win32-8_1 bienstman3: intel-win32-8_1 builtin_converters: intel-win32-8_1 callbacks: intel-win32-8_1 const_argument: intel-win32-8_1 crossmod_exception: intel-win32-8_1 data_members: intel-win32-8_1 defaults: intel-win32-8_1 dict: intel-win32-8_1 docstring: intel-win32-8_1 embedding: intel-win32-8_1 enum: intel-win32-8_1 exception_translator: intel-win32-8_1 extract: gcc-3.3.6-linux intel-win32-8_1 implicit: intel-win32-8_1 injected: intel-win32-8_1 iterator: intel-win32-8_1 keywords: intel-win32-8_1 list: gcc-3.3.6-linux intel-win32-8_1 long: intel-win32-8_1 map_indexing_suite: intel-win32-8_1 minimal: intel-win32-8_1 multi_arg_constructor: intel-win32-8_1 nested: intel-win32-8_1 object: intel-win32-8_1 opaque: intel-win32-8_1 operators: gcc-3.3.6-linux intel-win32-8_1 pearu1: intel-win32-8_1 pickle1: intel-win32-8_1 pickle2: intel-win32-8_1 pickle3: intel-win32-8_1 pickle4: intel-win32-8_1 polymorphism: intel-win32-8_1 polymorphism2: intel-win32-8_1 properties: intel-win32-8_1 raw_ctor: intel-win32-8_1 return_arg: intel-win32-8_1 shared_ptr: intel-win32-8_1 slice: gcc-3.3.6-linux intel-win32-8_1 staticmethod: intel-win32-8_1 str: intel-win32-8_1 test_pointer_adoption: intel-win32-8_1 try: intel-win32-8_1 tuple: intel-win32-8_1 vector_indexing_suite: intel-win32-8_1 virtual_functions: intel-win32-8_1 |random| random_test: intel-win32-8_1 intel-win32-8_1 intel-win32-8_1 |regex| regex_regress: intel-win32-8_1 regex_regress_dll: intel-win32-8_1 |serialization| test_array_text_archive_dll: cw-9_5-darwin test_array_text_warchive_dll: cw-9_5-darwin test_array_xml_archive_dll: cw-9_5-darwin test_array_xml_warchive_dll: cw-9_5-darwin test_binary_text_archive_dll: cw-9_5-darwin test_binary_text_warchive_dll: cw-9_5-darwin test_binary_xml_archive_dll: cw-9_5-darwin test_binary_xml_warchive_dll: cw-9_5-darwin test_class_info_load_binary_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_binary_archive_dll: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_archive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_archive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_warchive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_warchive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux vc-6_5 test_class_info_load_xml_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_archive_dll: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_warchive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_warchive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_save_text_archive_dll: cw-9_5-darwin test_class_info_save_text_warchive_dll: cw-9_5-darwin test_class_info_save_xml_warchive_dll: cw-9_5-darwin test_const_load_fail1: borland-5_6_4 test_const_load_fail1_nvp: borland-5_6_4 test_const_load_fail2: borland-5_6_4 test_const_load_fail2_nvp: borland-5_6_4 test_const_save_fail1: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_const_save_fail2: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_const_save_fail3: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_contained_class_text_archive_dll: cw-9_5-darwin test_contained_class_text_warchive_dll: cw-9_5-darwin test_contained_class_xml_archive_dll: cw-9_5-darwin test_contained_class_xml_warchive_dll: cw-9_5-darwin test_cyclic_ptrs_text_archive_dll: cw-9_5-darwin test_cyclic_ptrs_text_warchive_dll: cw-9_5-darwin test_cyclic_ptrs_xml_archive_dll: cw-9_5-darwin test_cyclic_ptrs_xml_warchive_dll: cw-9_5-darwin test_delete_pointer_text_archive_dll: cw-9_5-darwin test_delete_pointer_text_warchive_dll: cw-9_5-darwin test_delete_pointer_xml_archive_dll: cw-9_5-darwin test_delete_pointer_xml_warchive_dll: cw-9_5-darwin test_demo: intel-win32-8_1 test_demo_auto_ptr_dll: cw-9_5-darwin test_demo_dll: cw-9_4 cw-9_4 cw-9_5-darwin test_demo_exception: intel-win32-8_1 test_demo_exception_dll: cw-9_4 cw-9_4 cw-9_5-darwin test_demo_fast_archive_dll: msvc vc-6_5 test_demo_pimpl_dll: cw-9_5-darwin msvc vc-6_5 vc-7_0 test_demo_polymorphic_dll: cw-9_5-darwin test_demo_portable_archive: intel-win32-8_1 intel-win32-8_1 intel-win32-8_1 vc-7_0 vc-7_1 vc-8_0 test_demo_portable_archive_dll: intel-win32-8_1 intel-win32-8_1 intel-win32-8_1 test_demo_shared_ptr: cw-9_4 cw-9_4 cw-9_5-darwin test_demo_shared_ptr_dll: cw-9_4 cw-9_4 cw-9_5-darwin msvc vc-6_5 vc-7_0 test_demo_xml_load: intel-win32-8_1 test_demo_xml_save: intel-win32-8_1 test_deque_text_archive_dll: cw-9_5-darwin test_deque_text_warchive_dll: cw-9_5-darwin test_deque_xml_archive_dll: cw-9_5-darwin test_deque_xml_warchive_dll: cw-9_5-darwin test_derived_class_ptr_text_archive_dll: cw-9_5-darwin test_derived_class_ptr_text_warchive_dll: cw-9_5-darwin test_derived_class_ptr_xml_archive_dll: cw-9_5-darwin test_derived_class_ptr_xml_warchive_dll: cw-9_5-darwin test_derived_class_text_archive_dll: cw-9_5-darwin test_derived_class_text_warchive_dll: cw-9_5-darwin test_derived_class_xml_archive_dll: cw-9_5-darwin test_derived_class_xml_warchive_dll: cw-9_5-darwin test_derived_text_archive_dll: cw-9_5-darwin test_derived_text_warchive_dll: cw-9_5-darwin test_derived_xml_warchive_dll: cw-9_5-darwin test_diamond_binary_archive: cw-8_3 cw-9_5-darwin test_diamond_binary_archive_dll: cw-9_5-darwin test_diamond_text_archive: cw-8_3 cw-9_5-darwin test_diamond_text_archive_dll: cw-9_5-darwin test_diamond_text_warchive: cw-8_3 cw-9_5-darwin test_diamond_text_warchive_dll: cw-9_5-darwin test_diamond_xml_archive: cw-8_3 cw-9_5-darwin test_diamond_xml_archive_dll: cw-9_5-darwin test_diamond_xml_warchive: cw-8_3 cw-9_5-darwin test_diamond_xml_warchive_dll: cw-9_5-darwin test_list_ptrs_text_archive_dll: cw-9_5-darwin test_list_ptrs_text_warchive_dll: cw-9_5-darwin test_list_ptrs_xml_archive_dll: cw-9_5-darwin test_list_ptrs_xml_warchive_dll: cw-9_5-darwin test_list_text_archive_dll: cw-9_5-darwin test_list_text_warchive_dll: cw-9_5-darwin test_list_xml_archive_dll: cw-9_5-darwin test_list_xml_warchive_dll: cw-9_5-darwin test_map_binary_archive_dll: msvc vc-6_5 vc-7_0 test_map_text_archive_dll: cw-9_5-darwin msvc vc-6_5 vc-7_0 test_map_text_warchive_dll: cw-9_5-darwin msvc vc-6_5 vc-7_0 test_map_xml_archive_dll: cw-9_5-darwin test_map_xml_warchive_dll: cw-9_5-darwin test_mi_text_warchive_dll: intel-win32-8_1 test_mult_archive_types: cw-9_4 cw-9_4 cw-9_5-darwin test_mult_archive_types_dll: cw-9_4 cw-9_4 cw-9_5-darwin msvc vc-6_5 test_multiple_ptrs_text_archive_dll: cw-9_5-darwin test_multiple_ptrs_text_warchive_dll: cw-9_5-darwin test_multiple_ptrs_xml_archive_dll: cw-9_5-darwin test_multiple_ptrs_xml_warchive_dll: cw-9_5-darwin test_no_rtti_text_archive_dll: intel-win32-8_1 test_non_default_ctor_text_archive_dll: cw-9_5-darwin test_non_default_ctor_text_warchive_dll: cw-9_5-darwin test_non_default_ctor_xml_archive_dll: cw-9_5-darwin test_non_default_ctor_xml_warchive_dll: cw-9_5-darwin test_non_intrusive_text_archive_dll: cw-9_5-darwin test_non_intrusive_text_warchive_dll: cw-9_5-darwin test_non_intrusive_xml_archive_dll: cw-9_5-darwin test_non_intrusive_xml_warchive_dll: cw-9_5-darwin test_null_ptr_text_archive_dll: cw-9_5-darwin test_null_ptr_text_warchive_dll: cw-9_5-darwin test_null_ptr_xml_warchive_dll: cw-9_5-darwin test_nvp_text_archive_dll: cw-9_5-darwin test_nvp_text_warchive_dll: cw-9_5-darwin test_nvp_xml_archive_dll: cw-9_5-darwin test_nvp_xml_warchive_dll: cw-9_5-darwin test_object_text_warchive_dll: cw-9_5-darwin test_object_xml_warchive_dll: cw-9_5-darwin test_optional_text_archive_dll: cw-9_5-darwin test_optional_text_warchive_dll: cw-9_5-darwin test_optional_xml_archive_dll: cw-9_5-darwin test_optional_xml_warchive_dll: cw-9_5-darwin test_polymorphic_text_archive_dll: cw-9_5-darwin test_polymorphic_text_warchive_dll: cw-9_5-darwin test_polymorphic_xml_archive_dll: cw-9_5-darwin test_polymorphic_xml_warchive_dll: cw-9_5-darwin test_primitive_text_warchive_dll: cw-9_5-darwin test_primitive_xml_warchive_dll: cw-9_5-darwin test_private_ctor_dll: cw-9_5-darwin test_recursion_text_archive_dll: cw-9_5-darwin test_recursion_text_warchive_dll: cw-9_5-darwin test_recursion_xml_archive_dll: cw-9_5-darwin test_recursion_xml_warchive_dll: cw-9_5-darwin test_reset_object_address_dll: cw-9_5-darwin test_set_text_archive_dll: cw-9_5-darwin test_set_text_warchive_dll: cw-9_5-darwin test_set_xml_archive_dll: cw-9_5-darwin test_set_xml_warchive_dll: cw-9_5-darwin test_shared_ptr_132_binary_archive: borland-5_6_4 test_shared_ptr_132_binary_archive_dll: borland-5_6_4 test_shared_ptr_132_text_archive: borland-5_6_4 test_shared_ptr_132_text_archive_dll: borland-5_6_4 test_shared_ptr_132_text_warchive: borland-5_6_4 test_shared_ptr_132_text_warchive_dll: borland-5_6_4 test_shared_ptr_132_xml_archive: borland-5_6_4 test_shared_ptr_132_xml_archive_dll: borland-5_6_4 test_shared_ptr_132_xml_warchive: borland-5_6_4 test_shared_ptr_132_xml_warchive_dll: borland-5_6_4 test_simple_class_ptr_text_archive_dll: cw-9_5-darwin test_simple_class_ptr_text_warchive_dll: cw-9_5-darwin test_simple_class_ptr_xml_archive_dll: cw-9_5-darwin test_simple_class_ptr_xml_warchive_dll: cw-9_5-darwin test_simple_class_text_archive_dll: cw-9_5-darwin test_simple_class_text_warchive_dll: cw-9_5-darwin test_simple_class_xml_archive_dll: cw-9_5-darwin test_simple_class_xml_warchive_dll: cw-9_5-darwin test_split_text_archive_dll: cw-9_5-darwin test_split_text_warchive_dll: cw-9_5-darwin test_split_xml_warchive_dll: cw-9_5-darwin test_tracking_text_archive_dll: cw-9_5-darwin test_tracking_text_warchive_dll: cw-9_5-darwin test_tracking_xml_warchive_dll: cw-9_5-darwin test_variant_text_archive_dll: cw-9_5-darwin test_variant_text_warchive_dll: cw-9_5-darwin test_variant_xml_archive_dll: cw-9_5-darwin test_variant_xml_warchive_dll: cw-9_5-darwin test_vector_text_archive_dll: cw-9_5-darwin test_vector_text_warchive_dll: cw-9_5-darwin test_vector_xml_archive_dll: cw-9_5-darwin test_vector_xml_warchive_dll: cw-9_5-darwin |spirit| bug_fixes: cw-9_5-darwin bug_fixes_debug: cw-9_5-darwin numerics_tests: gcc-3.2.3-linux numerics_tests_debug: gcc-3.2.3-linux owi_mt_tests: gcc-3_3-darwin |test| errors_handling_test: cw-9_5-darwin vc-8_0 test_fp_comparisons: borland-5_6_4 test_tools_test: cw-9_4 cw-9_4 cw-9_5-darwin |thread| test_read_write_mutex: borland-5_6_4 test_thread_lib: cw-8_3 |wave| testwave: cw-8_3 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux
Douglas Gregor wrote:
353 failures in 14 libraries: bind (1)
bind| mem_fn_eq_test: intel-win32-8_1
This is an EDG bug. The same test is passing for other intel-win32-8_1 testers, so my theory is that the failure is due to an unpatched compiler. It is not a regression.
On Jun 30, 2005, at 4:42 PM, Peter Dimov wrote:
Douglas Gregor wrote:
353 failures in 14 libraries: bind (1)
bind| mem_fn_eq_test: intel-win32-8_1
This is an EDG bug. The same test is passing for other intel-win32-8_1 testers, so my theory is that the failure is due to an unpatched compiler. It is not a regression.
I see that quite a few libraries are failing for that particular tester but not for other intel-win32-8_1 testers. Paul, would it be possible to upgrade to the latest Intel 8.1 revision? Doug
Paul, would it be possible to upgrade to the latest Intel 8.1 revision?
I am out by maybe a week or two in keeping up with the latest as these were run on v8.1.028 (I'm not going to migrate to 9.0 for a little while yet). Are we sure that the fact I'm running a release build (which is NOT the default but is what most users would be interested in) is not the cause? Does anyone else run a release build on Intel. Incidentaly I run a release build because you asked me to run something different from existing testers :) I'll upgrade to latest v8 (if its changed) and run a release and a debug build over the next couple of days. The only thing of note with these tests is that random_tests.exe hangs (needing an end process) and that the whole process takes 12+ hrs for a full build, just release on an Athlon XP 2700+
Paul Baxter wrote:
Paul, would it be possible to upgrade to the latest Intel 8.1 revision?
I am out by maybe a week or two in keeping up with the latest as these were run on v8.1.028 (I'm not going to migrate to 9.0 for a little while yet).
Are we sure that the fact I'm running a release build (which is NOT the default but is what most users would be interested in) is not the cause?
For mem_fn_eq_test, almost certainly. It's a frontend bug. http://lists.boost.org/boost/2004/02/2076.php
I see that quite a few libraries are failing for that particular tester but not for other intel-win32-8_1 testers.
Paul, would it be possible to upgrade to the latest Intel 8.1 revision?
I noted that I was running a release build previously but have now uploaded a debug build that compares very closely with Stefan's latest. (minor compile difference in graph/graphviz compilation) Using v8.1.028 Intel. Note that Stefan reports using v8.1.027 (not sure about Beman) so perhaps many of those failures were release build after all. Unfortunately my previous results had been wiped from the summary chart so I wasn't able to compare in detail. In terms of compiler status, if there really is an issue between debug and release (usually bad compiler optimisations) shouldn't we: a) clearly note in the test report we're in debug or release build (can also be discovered by looking at the build directory name) b) Actually test a compiler using a reasonable set of optimisations since we're trying to report if a compiler can use Boost in actual builds, not in a no optimisation alternative. Paul
On Jul 3, 2005, at 5:31 AM, Paul Baxter wrote:
In terms of compiler status, if there really is an issue between debug and release (usually bad compiler optimisations) shouldn't we: a) clearly note in the test report we're in debug or release build (can also be discovered by looking at the build directory name)
b) Actually test a compiler using a reasonable set of optimisations since we're trying to report if a compiler can use Boost in actual builds, not in a no optimisation alternative.
I hadn't realized you were running a release built. It is very important to do (for many reasons), but I think we should add "-release" to the end of the toolset name to indicate what we're doing. Then we can more immediately see what problems are caused by compiler optimizations. Doug
Douglas Gregor <doug.gregor@gmail.com> writes:
On Jul 3, 2005, at 5:31 AM, Paul Baxter wrote:
In terms of compiler status, if there really is an issue between debug and release (usually bad compiler optimisations) shouldn't we: a) clearly note in the test report we're in debug or release build (can also be discovered by looking at the build directory name)
b) Actually test a compiler using a reasonable set of optimisations since we're trying to report if a compiler can use Boost in actual builds, not in a no optimisation alternative.
I hadn't realized you were running a release built. It is very important to do (for many reasons), but I think we should add "-release" to the end of the toolset name to indicate what we're doing. Then we can more immediately see what problems are caused by compiler optimizations.
It's also important to check through all of our tests to make sure they're not using "assert" and/or to force NDEBUG to be undefined. Otherwise many of our tests could be passing because they have no code to execute. -- Dave Abrahams Boost Consulting www.boost-consulting.com
On Jul 5, 2005, at 7:59 AM, David Abrahams wrote:
Douglas Gregor <doug.gregor@gmail.com> writes:
On Jul 3, 2005, at 5:31 AM, Paul Baxter wrote:
In terms of compiler status, if there really is an issue between debug and release (usually bad compiler optimisations) shouldn't we: a) clearly note in the test report we're in debug or release build (can also be discovered by looking at the build directory name)
b) Actually test a compiler using a reasonable set of optimisations since we're trying to report if a compiler can use Boost in actual builds, not in a no optimisation alternative.
I hadn't realized you were running a release built. It is very important to do (for many reasons), but I think we should add "-release" to the end of the toolset name to indicate what we're doing. Then we can more immediately see what problems are caused by compiler optimizations.
It's also important to check through all of our tests to make sure they're not using "assert" and/or to force NDEBUG to be undefined. Otherwise many of our tests could be passing because they have no code to execute.
Well, we *should* be using BOOST_CHECK, because we want assert()s in library code to disappear for release builds to be sure we haven't put an important side effect in them. Doug
Doug Gregor <dgregor@cs.indiana.edu> writes:
On Jul 5, 2005, at 7:59 AM, David Abrahams wrote:
Douglas Gregor <doug.gregor@gmail.com> writes:
On Jul 3, 2005, at 5:31 AM, Paul Baxter wrote:
In terms of compiler status, if there really is an issue between debug and release (usually bad compiler optimisations) shouldn't we: a) clearly note in the test report we're in debug or release build (can also be discovered by looking at the build directory name)
b) Actually test a compiler using a reasonable set of optimisations since we're trying to report if a compiler can use Boost in actual builds, not in a no optimisation alternative.
I hadn't realized you were running a release built. It is very important to do (for many reasons), but I think we should add "-release" to the end of the toolset name to indicate what we're doing. Then we can more immediately see what problems are caused by compiler optimizations.
It's also important to check through all of our tests to make sure they're not using "assert" and/or to force NDEBUG to be undefined. Otherwise many of our tests could be passing because they have no code to execute.
Well, we *should* be using BOOST_CHECK, because we want assert()s in library code to disappear for release builds to be sure we haven't put an important side effect in them.
Maybe we *should* but there are plenty of tests lying around that predate it. -- Dave Abrahams Boost Consulting www.boost-consulting.com
participants (6)
-
David Abrahams -
Doug Gregor -
Douglas Gregor
-
Douglas Gregor -
Paul Baxter -
Peter Dimov