Boost regression notification (2005-10-10 [RC_1_33_0])
Boost regression test failures ------------------------------ Report time: 2005-10-10T14:07:23Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/is... 217 failures in 5 libraries: graph (1) iostreams (1) range (3) serialization (207) spirit (5) |graph| graphviz_test: cw-9_4 |iostreams| gzip_test: gcc-4_0-darwin |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_binary_text_archive: vc-7_1 test_binary_text_archive_dll: vc-7_1 test_class_info_save_text_archive: vc-7_1 test_class_info_save_text_archive_dll: vc-7_1 test_demo_polymorphic: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_demo_polymorphic_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_derived_text_archive: vc-7_1 test_derived_text_archive_dll: vc-7_1 test_diamond_binary_archive: gcc-3_3-darwin test_diamond_binary_archive_dll: gcc-3_3-darwin test_diamond_text_archive: gcc-3_3-darwin test_diamond_text_archive_dll: gcc-3_3-darwin test_diamond_text_warchive: gcc-3_3-darwin test_diamond_text_warchive_dll: gcc-3_3-darwin test_diamond_xml_archive: gcc-3_3-darwin test_diamond_xml_archive_dll: gcc-3_3-darwin test_diamond_xml_warchive: gcc-3_3-darwin test_diamond_xml_warchive_dll: gcc-3_3-darwin test_exported_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-9.0-linux vc-6_5 test_exported_binary_archive_dll: gcc-4.0.1-linux vc-6_5 test_exported_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux vc-6_5 vc-7_1 test_exported_text_warchive: gcc-4.0.1-linux vc-6_5 test_exported_text_warchive_dll: gcc-4.0.1-linux vc-6_5 test_exported_xml_archive: gcc-4.0.1-linux intel-8.1-linux vc-6_5 test_exported_xml_archive_dll: gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_exported_xml_warchive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-6_5 test_map_binary_archive: gcc-3_3-darwin test_map_binary_archive_dll: gcc-3_3-darwin test_map_text_archive: gcc-3_3-darwin test_map_text_archive_dll: gcc-3_3-darwin test_map_text_warchive: gcc-3_3-darwin test_map_text_warchive_dll: gcc-3_3-darwin test_map_xml_archive: gcc-3_3-darwin test_map_xml_archive_dll: gcc-3_3-darwin test_map_xml_warchive: gcc-3_3-darwin test_map_xml_warchive_dll: gcc-3_3-darwin test_mi_text_archive: vc-7_1 test_mi_text_archive_dll: vc-7_1 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_non_default_ctor2_text_archive: vc-7_1 test_non_default_ctor2_text_archive_dll: vc-7_1 test_non_default_ctor_text_archive: vc-7_1 test_non_default_ctor_text_archive_dll: vc-7_1 test_non_intrusive_text_archive: vc-7_1 test_non_intrusive_text_archive_dll: vc-7_1 test_null_ptr_text_archive: vc-7_1 test_null_ptr_text_archive_dll: vc-7_1 test_object_text_archive: vc-7_1 test_object_text_archive_dll: vc-7_1 test_polymorphic_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_polymorphic_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos vc-7_1 test_primitive_text_archive: vc-7_1 test_primitive_text_archive_dll: vc-7_1 test_registered_text_archive: vc-7_1 test_registered_text_archive_dll: vc-7_1 test_set_binary_archive: gcc-3_3-darwin test_set_binary_archive_dll: gcc-3_3-darwin test_set_text_archive: gcc-3_3-darwin test_set_text_archive_dll: gcc-3_3-darwin test_set_text_warchive: gcc-3_3-darwin test_set_text_warchive_dll: gcc-3_3-darwin test_set_xml_archive: gcc-3_3-darwin test_set_xml_archive_dll: gcc-3_3-darwin test_set_xml_warchive: gcc-3_3-darwin test_set_xml_warchive_dll: gcc-3_3-darwin test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 test_split_text_archive: vc-7_1 test_split_text_archive_dll: vc-7_1 test_tracking_text_archive: vc-7_1 test_tracking_text_archive_dll: vc-7_1 test_unregistered_binary_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_binary_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_text_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_text_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux vc-7_1 test_unregistered_xml_archive: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux intel-8.1-linux intel-9.0-linux test_unregistered_xml_warchive: gcc-4.0.1-linux test_unregistered_xml_warchive_dll: gcc-4.0.1-linux |spirit| bug_000008: gcc-3_4_3-sunos grammar_mt_tests: gcc-3_4_3-sunos owi_mt_tests: gcc-3_4_3-sunos scoped_lock_tests: gcc-3_4_3-sunos scoped_lock_tests_debug: gcc-3_4_3-sunos
Douglas Gregor wrote:
Boost regression test failures ------------------------------ Report time: 2005-10-10T14:07:23Z
iostreams (1)
This failure is old (from Friday). I haven't been following the discussions about regression reporting lately, so I don't know if this is a problem I should report to someone or if this is the way it's supposed to work. At any rate, as soon as the tests are rerun for this platform, everything should pass. -- Jonathan Turkanis www.kangaroologic.com
On 10/10/05, Douglas Gregor <dgregor@cs.indiana.edu> wrote:
|spirit| bug_000008: gcc-3_4_3-sunos grammar_mt_tests: gcc-3_4_3-sunos owi_mt_tests: gcc-3_4_3-sunos scoped_lock_tests: gcc-3_4_3-sunos scoped_lock_tests_debug: gcc-3_4_3-sunos
See:* *http://tinyurl.com/8jg2h These failures all appear to be due to unresolved externals when linking with Boost.Threads (nanosleep, sched_yield). I'm claiming major bjam ignorance, so I need help fixing this: how can I ensure that -lrt is included in the link libraries when these tests are built? -- Caleb Epstein caleb dot epstein at gmail dot com
Caleb Epstein wrote:
On 10/10/05, Douglas Gregor <dgregor@cs.indiana.edu> wrote:
|spirit| bug_000008: gcc-3_4_3-sunos grammar_mt_tests: gcc-3_4_3-sunos owi_mt_tests: gcc-3_4_3-sunos scoped_lock_tests: gcc-3_4_3-sunos scoped_lock_tests_debug: gcc-3_4_3-sunos
See:* *http://tinyurl.com/8jg2h
These failures all appear to be due to unresolved externals when linking with Boost.Threads (nanosleep, sched_yield). I'm claiming major bjam ignorance, so I need help fixing this: how can I ensure that -lrt is included in the link libraries when these tests are built?
Well there's already handling in gcc-tools.jam to add the -lrt when running in SunOS. It tests that uname is of the "SunOS*" form. What does uname return on that machine? Oh, I think I see the problem. The test you pointed to isn't being built as multi-threaded. The build requirements for those tests need to have "<threading>multi" added so that it links in the thread libraries. Grr, except it looks like the Spirit tests are already trying to add that requirement. -- -- 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
On 10/10/05, Rene Rivera <grafik.list@redshift-software.com> wrote:
Caleb Epstein wrote:
On 10/10/05, Douglas Gregor <dgregor@cs.indiana.edu> wrote:
|spirit| bug_000008: gcc-3_4_3-sunos grammar_mt_tests: gcc-3_4_3-sunos owi_mt_tests: gcc-3_4_3-sunos scoped_lock_tests: gcc-3_4_3-sunos scoped_lock_tests_debug: gcc-3_4_3-sunos
See:* *http://tinyurl.com/8jg2h
These failures all appear to be due to unresolved externals when linking with Boost.Threads (nanosleep, sched_yield). I'm claiming major bjam ignorance, so I need help fixing this: how can I ensure that -lrt is included in the link libraries when these tests are built?
Well there's already handling in gcc-tools.jam to add the -lrt when running in SunOS. It tests that uname is of the "SunOS*" form. What does uname return on that machine?
Oh, I think I see the problem. The test you pointed to isn't being built as multi-threaded. The build requirements for those tests need to have "<threading>multi" added so that it links in the thread libraries.
Grr, except it looks like the Spirit tests are already trying to add that requirement.
BTW, I committed today a changed to expected-failures-markup.xml that removed some expected failures for the Boost.Threads gcc-on-sunos case. The code used to link with -static, which didn't work since there are no static versions of some libs. But it looks like you or someone else fixed it to just name archive libraries using fully-qualified paths and now the tests compile and run OK. This is on the RC_1_33_0 branch. -- Caleb Epstein caleb dot epstein at gmail dot com
These failures all appear to be due to unresolved externals when linking with Boost.Threads (nanosleep, sched_yield). I'm claiming major bjam ignorance, so I need help fixing this: how can I ensure that -lrt is included in the link libraries when these tests are built?
I believe I've already committed a fix for this: there was a minor snafu in the Spirit Jamfile that meant that <threading>multi wasn't getting applied whenever the BUILD environment variable was set. John.
John Maddock wrote:
These failures all appear to be due to unresolved externals when linking with Boost.Threads (nanosleep, sched_yield). I'm claiming major bjam ignorance, so I need help fixing this: how can I ensure that -lrt is included in the link libraries when these tests are built?
I believe I've already committed a fix for this: there was a minor snafu in the Spirit Jamfile that meant that <threading>multi wasn't getting applied whenever the BUILD environment variable was set.
That explains why I couldn't find anything wrong with the Jamfile. But it also means that Caleb is going to have to delete the spirit tests so they get rebuilt, since he runs in incremental mode. Or if just does a full run. -- -- 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
On 10/11/05, Rene Rivera <grafik.list@redshift-software.com> wrote:
That explains why I couldn't find anything wrong with the Jamfile. But it also means that Caleb is going to have to delete the spirit tests so they get rebuilt, since he runs in incremental mode. Or if just does a full run.
Re-running tests now without --incremental. I think they'll take the better part of the day. -- Caleb Epstein caleb dot epstein at gmail dot com
participants (5)
-
Caleb Epstein -
Douglas Gregor -
John Maddock -
Jonathan Turkanis -
Rene Rivera