Boost regression notification (2005-09-02 [HEAD])

Boost regression test failures ------------------------------ Report time: 2005-09-02T05:00:11Z 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. typeof Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues.... 89 failures in 14 libraries: foreach (8) function (1) graph (4) lambda (2) math (6) mpl (3) parameter (4) random (2) serialization (40) spirit (2) test (1) thread (8) typeof (4) wave (4) |foreach| rvalue_const: gcc-4_0-darwin rvalue_nonconst: gcc-4_0-darwin user_defined: cw-8_3 cw-9_4 msvc vc-6_5 vc-6_5-stlport vc-7_0 |function| lambda_test: gcc-4_0-darwin |graph| graphviz_test: vc-7_1 vc-7_1 vc-7_1 layout_test: intel-win32-9_0 |lambda| bind_tests_simple_f_refs: gcc-4_0-darwin exception_test: gcc-4_0-darwin |math| octonion_test: gcc-4_0-darwin gcc-4_0-darwin quaternion_test: gcc-4_0-darwin gcc-4_0-darwin special_functions_test: gcc-4_0-darwin gcc-4_0-darwin |mpl| integral_c: gcc-4_0-darwin size_t: gcc-4_0-darwin gcc-4_0-darwin |parameter| basics: borland-5_6_4 macros: borland-5_6_4 sfinae: borland-5_6_4 unnamed: borland-5_6_4 |random| random_demo: gcc-4_0-darwin random_test: gcc-4_0-darwin |serialization| test_class_info_load_binary_archive: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |test| token_iterator_test: gcc-4_0-darwin |thread| test_barrier_lib: intel-9.0-linux test_condition_lib: intel-9.0-linux test_mutex_lib: intel-9.0-linux test_once_lib: intel-9.0-linux test_read_write_mutex_lib: intel-9.0-linux test_thread_lib: intel-9.0-linux test_tss_lib: intel-9.0-linux test_xtime_lib: intel-9.0-linux |typeof| type_emulation: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux type_native: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |wave| test_re2c_lexer: intel-9.0-linux test_slex_lexer: intel-9.0-linux testwave: gcc-3.3.6-linux intel-9.0-linux

"Douglas Gregor" <dgregor@cs.indiana.edu> wrote
http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues.... What is the exact difference between: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/typeof_... linked by the page above, and: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/typeof.... linked by the Boost home page? Debug versus *release* mode or is it somehow related to the current *release*? Why do they contain different number of columns? Thanks, Arkadiy

Arkadiy Vertleyb wrote:
The former only lists compilers that are supported and required for doing a _Boost release_. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org

Doug Gregor wrote:
There are problems with Comeau on Windows. One problem is that Comeau does not fully support dynamic libraries, and the other that it is not obvious what "standard conformity level" should be selected for this compiler (ie. non-strict, strict warnings --a or strict --A). Compiler running in non-strict accepts OS headers, but then it is also least portable (it emulates bugs specific to other compilers on this platform). Hopefully next version will have better support for shared libraries and will accept OS headers in strict mode. I do not know if these issues apply to other platforms. It would be nice to support Comeau in strict (or strict warnings) mode on at least one combination platform + backend C compiler. B.

Arkadiy Vertleyb wrote:
Popularity is usually at the bottom of the considerations in this case. Consistent testing resources, and enough feature support tend to come first. For example DLLs are a problem with como, so it renders many of the tests inoperable. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org
participants (5)
-
Arkadiy Vertleyb
-
Bronek Kozicki
-
Doug Gregor
-
Douglas Gregor
-
Rene Rivera