Boost regression notification (2006-11-22 [RC_1_34_0])

Boost Regression test failures Report time: 2006-11-22T10:27:55Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/is... 205 failures in 20 libraries concept_check (60) date_time (3) io (1) iostreams (10) iterator (3) lambda (1) math (26) mpl (3) numeric/interval (2) optional (1) parameter (2) python (58) random (1) serialization (8) signals (4) spirit (2) statechart (6) test (12) thread (1) utility (1) |concept_check| class_concept_fail_expected: borland-5.6.4 borland-5.8.2 borland-5.8.2 cw-9.4 darwin-4.0.1 gcc-3.2.3_linux gcc-3.3.6 gcc-3.3.6_linux gcc-3.4.4 gcc-3.4.5_linux gcc-3.4.5_linux_x86_64 gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.0_linux_x86_64 gcc-4.1.1_sunos_i86pc hp_cxx-71_006_tru64 intel-linux-9.0 intel-vc71-win-9.1 intel-vc8-win-9.1 msvc-6.5 msvc-7.0 msvc-7.1 msvc-7.1 msvc-8.0 msvc-8.0 qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp sun-5.8 concept_check_fail_expected: borland-5.6.4 borland-5.8.2 borland-5.8.2 cw-9.4 darwin-4.0.1 gcc-3.2.3_linux gcc-3.3.6 gcc-3.3.6_linux gcc-3.4.4 gcc-3.4.5_linux gcc-3.4.5_linux_x86_64 gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.0_linux_x86_64 gcc-4.1.1_sunos_i86pc hp_cxx-71_006_tru64 intel-linux-9.0 intel-vc71-win-9.1 intel-vc8-win-9.1 msvc-6.5 msvc-7.0 msvc-7.1 msvc-7.1 msvc-8.0 msvc-8.0 qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp sun-5.8 |date_time| testconstrained_value: qcc-3.3.5_cpp testduration: borland-5.8.2 testgenerators_dll: gcc-4.1.0_linux |io| ios_state_test: borland-5.8.2 |iostreams| bzip2_test: msvc-7.1 msvc-8.0 file_descriptor_test: cw-9.4 finite_state_filter_test: cw-9.4 gzip_test: msvc-7.1 msvc-8.0 mapped_file_test: cw-9.4 newline_test: borland-5.8.2 zlib_test: msvc-7.1 msvc-8.0 |iterator| filter_iterator_test: borland-5.8.2 lvalue_concept_fail: borland-5.8.2 msvc-7.1 |lambda| bind_tests_simple: intel-linux-9.0 |math| common_factor_test: borland-5.8.2 cw-9.4 darwin-4.0.1 gcc-3.2.3_linux gcc-3.3.6 gcc-3.3.6_linux gcc-3.4.4 gcc-3.4.5_linux gcc-3.4.5_linux_x86_64 gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.0_linux_x86_64 gcc-4.1.1_sunos_i86pc hp_cxx-71_006_tru64 intel-linux-9.0 intel-vc71-win-9.1 intel-vc8-win-9.1 msvc-6.5 msvc-7.0 msvc-7.1 msvc-7.1 msvc-8.0 msvc-8.0 qcc-3.3.5_cpp qcc-3.3.5_gpp sun-5.8 |mpl| int: borland-5.8.2 integral_c: borland-5.8.2 size_t: borland-5.8.2 |numeric/interval| mul: borland-5.8.2 test_float: borland-5.8.2 |optional| optional_test: borland-5.8.2 |parameter| preprocessor_deduced: qcc-3.3.5_gpp python_test: msvc-7.1 |python| andreas_beyer: msvc-7.1 args: msvc-7.1 auto_ptr: msvc-7.1 back_reference: msvc-7.1 ben_scott1: msvc-7.1 bienstman1: msvc-7.1 bienstman2: msvc-7.1 bienstman3: msvc-7.1 builtin_converters: msvc-7.1 callbacks: msvc-7.1 const_argument: msvc-7.1 crossmod_exception: msvc-7.1 crossmod_opaque: msvc-7.1 data_members: msvc-7.1 defaults: msvc-7.1 dict: msvc-7.1 docstring: msvc-7.1 enum: msvc-7.1 exception_translator: msvc-7.1 extract: msvc-7.1 implicit: msvc-7.1 injected: msvc-7.1 iterator: msvc-7.1 keywords: msvc-7.1 list: msvc-7.1 long: msvc-7.1 map_indexing_suite: msvc-7.1 minimal: msvc-7.1 multi_arg_constructor: msvc-7.1 nested: msvc-7.1 numpy: msvc-7.1 object: msvc-7.1 opaque: msvc-7.1 operators: msvc-7.1 pearu1: msvc-7.1 pickle1: msvc-7.1 pickle2: msvc-7.1 pickle3: msvc-7.1 pickle4: msvc-7.1 pointer_vector: msvc-7.1 polymorphism: msvc-7.1 polymorphism2: msvc-7.1 polymorphism2_auto_ptr: msvc-7.1 properties: msvc-7.1 raw_ctor: msvc-7.1 return_arg: msvc-7.1 shared_ptr: msvc-7.1 slice: msvc-7.1 staticmethod: msvc-7.1 stl_iterator: msvc-7.1 str: msvc-7.1 test_pointer_adoption: msvc-7.1 try: msvc-7.1 tuple: msvc-7.1 vector_indexing_suite: msvc-7.1 virtual_functions: msvc-7.1 voidptr: msvc-7.1 wrapper_held_type: msvc-7.1 |random| random_test: intel-linux-9.0 |serialization| test_map_text_archive: qcc-3.3.5_gpp test_reset_object_address: msvc-7.0 test_reset_object_address_dll: msvc-7.0 test_utf8_codecvt: borland-5.8.2 test_variant_xml_archive: borland-5.8.2 test_variant_xml_archive_dll: borland-5.8.2 test_variant_xml_warchive: borland-5.8.2 test_variant_xml_warchive_dll: borland-5.8.2 |signals| deletion_test: msvc-6.5 ordering_test: msvc-6.5 signal_n_test: msvc-6.5 trackable_test: msvc-6.5 |spirit| symbols_add_null: msvc-7.1 symbols_add_null_debug: msvc-7.1 |statechart| BitMachineExample: qcc-3.3.5_cpp qcc-3.3.5_gpp CameraExample: cw-9.4 PerformanceExample: cw-9.4 TransitionTestBoth: qcc-3.3.5_gpp TransitionTestRelaxed: qcc-3.3.5_gpp |test| prg_exec_fail1: intel-vc71-win-9.1 intel-vc8-win-9.1 msvc-6.5 msvc-7.0 msvc-7.1 msvc-8.0 prg_exec_fail2: darwin-4.0.1 prg_exec_fail3: borland-5.8.2 cw-9.4 msvc-7.1 test_case_template_test: borland-5.8.2 test_fp_comparisons: cw-9.4 |thread| test_tss_lib: borland-5.8.2 |utility| operators_test: gcc-3.4.5_linux_x86_64

Douglas Gregor wrote:
This test works fine on HEAD, but fails on RC branch. It's apparently caused by the fact that on HEAD, the test has: #define BOOST_TEST_MAIN "Boost.Math GCD & LCM unit tests" whereas on RC, it does not. In fact, delta from 1.4 to 1.8 of that file was never merged to RC. I've just merged and committed, assuming it's oversight. Test now works for me locally. - Volodya

On 11/23/06 3:18 AM, "Vladimir Prus" <ghost@cs.msu.su> wrote:
I don't know how to use branches, let alone how to cross-pollinate code between them. And I heard that messing up such operations is VERY bad. The bigger reason is that I've done changes on the HEAD that are more than bug fixes, which shouldn't happen as we are wrapping up 1.34. The biggest change to that library is adding the binary-Euclidean GCD algorithm for the built-in integer types. The biggest changes to the test file are switching to Boost.Test's unit-test system and explicitly checking numeric_limits compatibility. I noticed that only the test file was merged into the 1.34 branch, and the changed header file wasn't, which I guess only approaches the "bug-fixes only" line but doesn't cross it. Fortunately the new test file was still compatible with the old header file! On a related note, shouldn't the static-GCD class tests be compile-time tests, instead of run-time tests? How would I change that? I guess I would need to separate the code for the run-time and compile-time to separate files then mess around with the Boost.Build/Jam settings? (I have no idea how to create a compile-time test, or even what testing regimen Boost currently uses for that.) -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

Janek Kozicki <janek_listy@wp.pl> writes:
out of curiosity: are threads tested on multiprocessor machine?
The JustSoftwareSolutions tests are run on a dual-core machine, which is close enough for most purposes. Anthony -- Anthony Williams Software Developer Just Software Solutions Ltd http://www.justsoftwaresolutions.co.uk
participants (5)
-
Anthony Williams
-
Daryle Walker
-
Douglas Gregor
-
Janek Kozicki
-
Vladimir Prus