
I re-ran the boost tests this afternoon and here are the "interesting" lines from the output ...found 34702 targets... ...updating 529 targets... ...can't find 2 targets... ...can't make 4 targets... ...on 100th target... C:\Projects\boost\boost\numeric\interval\io.hpp(35) : error C2872: 'lower' : ambiguous symbol C:\Projects\boost\boost\numeric\interval\io.hpp(35) : error C2872: 'upper' : ambiguous symbol ...failed vc-C++ ..\bin\boost\libs\numeric\ublas\test7.test\vc7.1\debug\test71.obj... C:\Projects\boost\boost\numeric\interval\io.hpp(35) : error C2872: 'lower' : ambiguous symbol C:\Projects\boost\boost\numeric\interval\io.hpp(35) : error C2872: 'upper' : ambiguous symbol ...failed vc-C++ ..\bin\boost\libs\numeric\ublas\test7.test\vc7.1\debug\test72.obj... ...skipped <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test7.CMD for lack of <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test71.obj... ...skipped <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test7.exe for lack of <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test7.CMD... ...on 200th target... ...on 300th target... FAIL :: Caught unexpected exception during Stream in greg_month FAIL :: Caught unexpected exception during Stream in greg_month -- wide streams FAIL :: Bad month exception NOT caught (misspelled name) FAIL :: Caught unexpected exception during Stream in greg_weekday FAIL :: Caught unexpected exception during Stream in greg_weekday -- wide stream FAIL :: Bad weekday exception NOT caught (misspelled name) ...failed execute-test ..\bin\boost\libs\date_time\test\testfacet_dll.test\vc7.1\debug\testfacet_dll.run... FAIL :: Get time of day micro second clock not supported due to inadequate compiler ...failed execute-test ..\bin\boost\libs\date_time\test\testmicrosec_time_clock.test\vc7.1\debug\testmicrosec_time_clock.run... ...failed execute-test ..\bin\boost\libs\graph\test\adjacency_matrix_test.test\vc7.1\debug\adjacency_matrix_test.run... ...skipped <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test7.run for lack of <@boost!libs!numeric!ublas\test7.test\vc7.1\debug>test7.exe... ...failed execute-test ..\bin\boost\libs\python\test\slice.test\vc7.1\debug\slice.run... ...on 400th target... ...on 500th target... ...failed execute-test ..\bin\boost\libs\serialization\test\test_demo_xml_save.test\vc7.1\debug\test_demo_xml_save.run... ...failed execute-test ..\bin\boost\libs\serialization\test\test_demo_xml_load.test\vc7.1\debug\test_demo_xml_load.run... ...failed execute-test ..\bin\boost\libs\serialization\test\test_demo_xml.test\vc7.1\debug\test_demo_xml.run... ...failed execute-test ..\bin\boost\libs\serialization\test\test_demo_shared_ptr.test\vc7.1\debug\test_demo_shared_ptr.run... ...failed execute-test ..\bin\boost\libs\serialization\test\test_demo_exception.test\vc7.1\debug\test_demo_exception.run... ...failed execute-test ..\bin\boost\libs\serialization\test\test_demo.test\vc7.1\debug\test_demo.run... ../libs/thread/test/test_read_write_mutex.cpp(205): error in "test_read_write_mutex": test r1.m_value == 10 failed ...failed execute-test ..\bin\boost\libs\thread\test\test_read_write_mutex.test\vc7.1\debug\threading-multi\test_read_write_mutex.run... ../libs/test/test/ifstream_line_iterator_test.cpp(28): error in "test_default_delimeter": test it != utf::ifstream_line_iterator() failed ../libs/test/test/ifstream_line_iterator_test.cpp(30): error in "test_default_delimeter": test *it == "acv ffg" failed [ != acv ffg] ../libs/test/test/ifstream_line_iterator_test.cpp(36): error in "test_default_delimeter": test *it == " " failed [ != ] ../libs/test/test/ifstream_line_iterator_test.cpp(39): error in "test_default_delimeter": test *it == "1" failed [ != 1] ../libs/test/test/ifstream_line_iterator_test.cpp(51): error in "test_custom_delimeter": test it != utf::ifstream_line_iterator() failed ../libs/test/test/ifstream_line_iterator_test.cpp(53): error in "test_custom_delimeter": test *it == "{ abc d " failed [ != { abc d ] ../libs/test/test/ifstream_line_iterator_test.cpp(56): error in "test_custom_delimeter": test *it == "\n{ d \n dsfg\n" failed [ != ../libs/test/test/ifstream_line_iterator_test.cpp(59): error in "test_custom_delimeter": test *it == "\n" failed [ != ...failed execute-test ..\bin\boost\libs\test\test\ifstream_line_iterator_test.test\vc7.1\debug\ifstream_line_iterator_test.run... ...skipped <@boost!libs!test!test\result_report_test.test\vc7.1\debug>result_report_test.run for lack of C:\Projects\boost\libs\test\test\result_report_test.pattern... ...skipped <@boost!libs!test!test\errors_handling_test.test\vc7.1\debug>errors_handling_test.run for lack of C:\Projects\boost\libs\test\test\errors_handling_test.pattern... ...failed updating 14 targets... ...skipped 20 targets... ...updated 499 targets... The entire output log ( ftp://rudbek.com/pub/boost/status.log ) is available if one of the authors thinks it will be of assistance. The log from the v2 run is there also, but it has so many difficulties I'm not sure how useful it is. Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

On Sun, 18 Jul 2004 14:54:31 -0700, Victor A. Wagner Jr. wrote
I re-ran the boost tests this afternoon and here are the "interesting" lines from the output
My notes on the date-time issues:
...on 200th target... ...on 300th target... FAIL :: Caught unexpected exception during Stream in greg_month FAIL :: Caught unexpected exception during Stream in greg_month -- wide streams FAIL :: Bad month exception NOT caught (misspelled name) FAIL :: Caught unexpected exception during Stream in greg_weekday FAIL :: Caught unexpected exception during Stream in greg_weekday -- wide stream FAIL :: Bad weekday exception NOT caught (misspelled name) ...failed execute-test
These should be fixed on your next run -- pending any sourceforge CVS sync delays. We've come up with a workaround for this issue. ..\bin\boost\libs\date_time\test\testfacet_dll.test\vc7.1\debug\testfacet_dll.run...
FAIL :: Get time of day micro second clock not supported due to inadequate compiler ...failed execute-test ..\bin\boost\libs\date_time\test\testmicrosec_time_clock.test\vc7.1\debug\testmicrosec_time_clock.run... ...failed execute-test
We were lying in 1.31 when we showed this test as passing -- failure is the correct result for this platform/compiler. We will be marking the regression xml soon... Jeff
participants (2)
-
Jeff Garland
-
Victor A. Wagner Jr.