Boost regression notification (2005-10-18 [RC_1_33_0])
Boost regression test failures ------------------------------ Report time: 2005-10-18T15:24:21Z 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... 55 failures in 4 libraries: parameter (2) python (17) range (3) serialization (33) |parameter| tutorial: borland-5_6_4 gcc-2.95.3-linux |python| builtin_converters: cw-8_3 cw-9_4 gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.1-linux gcc-4_0-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 vc-6_5 vc-6_5-stlport vc-7_0 vc-7_1 |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_class_info_load_binary_archive: cw-9_4 test_class_info_load_binary_archive_dll: cw-9_4 intel-win32-8_1 test_class_info_load_text_archive: cw-9_4 test_class_info_load_text_archive_dll: cw-9_4 intel-win32-8_1 test_class_info_load_text_warchive: cw-9_4 test_class_info_load_text_warchive_dll: cw-9_4 intel-win32-8_1 test_class_info_load_xml_archive: cw-9_4 test_class_info_load_xml_archive_dll: cw-9_4 intel-win32-8_1 test_class_info_load_xml_warchive: cw-9_4 test_class_info_load_xml_warchive_dll: cw-9_4 intel-win32-8_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_shared_ptr_132_text_warchive: intel-win32-8_1 test_shared_ptr_binary_archive: borland-5_6_4 test_shared_ptr_binary_archive_dll: borland-5_6_4 test_shared_ptr_text_archive: borland-5_6_4 test_shared_ptr_text_archive_dll: borland-5_6_4 test_shared_ptr_text_warchive: borland-5_6_4 test_shared_ptr_text_warchive_dll: borland-5_6_4 test_shared_ptr_xml_archive: borland-5_6_4 test_shared_ptr_xml_archive_dll: borland-5_6_4 test_shared_ptr_xml_warchive: borland-5_6_4 test_shared_ptr_xml_warchive_dll: borland-5_6_4
|python| builtin_converters: cw-8_3 cw-9_4 gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.1-linux gcc-4_0-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 vc-6_5 vc-6_5-stlport vc-7_0 vc-7_1
This is directly related to a checkin some days ago. I tried to fix it by doing the obvious: diff -u -r1.17.6.1 test_builtin_converters.py --- test_builtin_converters.py 14 Oct 2005 15:54:40 -0000 1.17.6.1 +++ test_builtin_converters.py 19 Oct 2005 08:04:13 -0000 @@ -81,7 +81,7 @@
try: ... unicode -... catch: +... except: ... print "u'yo, wassup?'" ... else: ... eval("rewrap_value_wstring(u'yo, wassup?')") @@ -91,7 +91,7 @@
try: ... unicode -... catch: +... except: ... print "u'yo, wassup?'" ... else: ... eval("rewrap_value_string(u'yo, wassup?')")
But this didn't work. The error message now is: Trying: try: unicode except: print "u'yo, wassup?'" else: eval("rewrap_value_wstring(u'yo, wassup?')") Expecting: u'yo, wassup?' ********************************************************************** File "test_builtin_converters.py", line 82, in __main__ Failed example: try: unicode except: print "u'yo, wassup?'" else: eval("rewrap_value_wstring(u'yo, wassup?')") Expected: u'yo, wassup?' Got: <type 'unicode'> u'yo, wassup?' Trying: try: unicode except: print "u'yo, wassup?'" else: eval("rewrap_value_string(u'yo, wassup?')") Expecting: u'yo, wassup?' ********************************************************************** File "test_builtin_converters.py", line 92, in __main__ Failed example: try: unicode except: print "u'yo, wassup?'" else: eval("rewrap_value_string(u'yo, wassup?')") Expected: u'yo, wassup?' Got: <type 'unicode'> u'yo, wassup?' What is 'unicode' here supposed to be? Markus
Markus Schöpflin <markus.schoepflin@comsoft.de> writes:
|python| builtin_converters: cw-8_3 cw-9_4 gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.1-linux gcc-4_0-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 vc-6_5 vc-6_5-stlport vc-7_0 vc-7_1
This is directly related to a checkin some days ago. I tried to fix it by doing the obvious:
Thanks for the report; now fixed. -- Dave Abrahams Boost Consulting www.boost-consulting.com
participants (3)
-
David Abrahams -
Douglas Gregor -
Markus Schöpflin