[Report] 67 regressions on RC_1_34_0 (2007-03-30)

Boost Regression test failures Report time: 2007-03-30T05:25:01Z 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... 67 failures in 2 libraries parameter (4) python (63) |parameter| python_test: gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.1_sunos_i86pc gcc-cygwin-3.4.4 |python| andreas_beyer: gcc-4.1.1_sunos_i86pc args: gcc-4.1.1_sunos_i86pc auto_ptr: gcc-4.1.1_sunos_i86pc back_reference: gcc-4.1.1_sunos_i86pc bases: gcc-4.1.1_sunos_i86pc ben_scott1: gcc-4.1.1_sunos_i86pc bienstman1: gcc-4.1.1_sunos_i86pc bienstman2: gcc-4.1.1_sunos_i86pc bienstman3: gcc-4.1.1_sunos_i86pc builtin_converters: gcc-4.1.1_sunos_i86pc callbacks: gcc-4.1.1_sunos_i86pc const_argument: gcc-4.1.1_sunos_i86pc crossmod_exception: gcc-4.1.1_sunos_i86pc crossmod_opaque: gcc-4.1.1_sunos_i86pc data_members: gcc-4.1.1_sunos_i86pc defaults: gcc-4.1.1_sunos_i86pc dict: gcc-4.1.1_sunos_i86pc docstring: gcc-4.1.1_sunos_i86pc enum: gcc-4.1.1_sunos_i86pc exception_translator: gcc-4.1.1_sunos_i86pc exec-dynamic: gcc-4.1.1_sunos_i86pc extract: gcc-4.1.1_sunos_i86pc implicit: gcc-4.1.1_sunos_i86pc injected: gcc-4.1.1_sunos_i86pc iterator: gcc-4.1.1_sunos_i86pc keywords: gcc-4.1.1_sunos_i86pc list: gcc-4.1.1_sunos_i86pc long: gcc-4.1.1_sunos_i86pc map_indexing_suite: gcc-4.1.1_sunos_i86pc minimal: gcc-4.1.1_sunos_i86pc multi_arg_constructor: gcc-4.1.1_sunos_i86pc nested: gcc-4.1.1_sunos_i86pc numpy: gcc-4.1.1_sunos_i86pc object: gcc-4.1.1_sunos_i86pc opaque: gcc-4.1.1_sunos_i86pc operators: gcc-4.1.1_sunos_i86pc pearu1: gcc-4.1.1_sunos_i86pc pickle1: gcc-4.1.1_sunos_i86pc pickle2: gcc-4.1.1_sunos_i86pc pickle3: gcc-4.1.1_sunos_i86pc pickle4: gcc-4.1.1_sunos_i86pc pointee: gcc-4.1.1_sunos_i86pc pointer_type_id_test: gcc-4.1.1_sunos_i86pc pointer_vector: gcc-4.1.1_sunos_i86pc polymorphism: gcc-4.1.1_sunos_i86pc polymorphism2: gcc-4.1.1_sunos_i86pc polymorphism2_auto_ptr: gcc-4.1.1_sunos_i86pc properties: gcc-4.1.1_sunos_i86pc raw_ctor: gcc-4.1.1_sunos_i86pc return_arg: gcc-4.1.1_sunos_i86pc shared_ptr: gcc-4.1.1_sunos_i86pc slice: gcc-4.1.1_sunos_i86pc staticmethod: gcc-4.1.1_sunos_i86pc stl_iterator: gcc-4.1.1_sunos_i86pc str: gcc-4.1.1_sunos_i86pc test_pointer_adoption: gcc-4.1.1_sunos_i86pc try: gcc-4.1.1_sunos_i86pc tuple: gcc-4.1.1_sunos_i86pc upcast: gcc-4.1.1_sunos_i86pc vector_indexing_suite: gcc-4.1.1_sunos_i86pc virtual_functions: gcc-4.1.1_sunos_i86pc voidptr: gcc-4.1.1_sunos_i86pc wrapper_held_type: gcc-4.1.1_sunos_i86pc

Douglas Gregor wrote:
|parameter| python_test: gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.1_sunos_i86pc gcc-cygwin-3.4.4
These are already outdated results for gcc-4.0.3_linux and gcc-4.1.0_linux. The tests actually pass. The next table will reflect that state. Regards, m

Martin Wille wrote:
Douglas Gregor wrote:
|parameter| python_test: gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.1_sunos_i86pc gcc-cygwin-3.4.4
These are already outdated results for gcc-4.0.3_linux and gcc-4.1.0_linux. The tests actually pass. The next table will reflect that state.
What about 'gcc-4.1.1_sunos_i86pc' ? That seems to be a total failure. (The failure is at least partially in the regression harness; the table at http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/py... doesn't even mention it. :-( (Out of curiosity: what are you basing your decision on concerning when to spin a release candidate ?) Thanks, Stefan -- ...ich hab' noch einen Koffer in Berlin...

on Sun Apr 01 2007, Stefan Seefeld <seefeld-AT-sympatico.ca> wrote:
Martin Wille wrote:
Douglas Gregor wrote:
|parameter| python_test: gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.1_sunos_i86pc gcc-cygwin-3.4.4
These are already outdated results for gcc-4.0.3_linux and gcc-4.1.0_linux. The tests actually pass. The next table will reflect that state.
What about 'gcc-4.1.1_sunos_i86pc' ? That seems to be a total failure. (The failure is at least partially in the regression harness; the table at http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/py... doesn't even mention it. :-(
Huh? I see it there. Looks all green to me. What am I missing? -- Dave Abrahams Boost Consulting www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com

David Abrahams wrote:
on Sun Apr 01 2007, Stefan Seefeld <seefeld-AT-sympatico.ca> wrote:
Martin Wille wrote:
Douglas Gregor wrote:
|parameter| python_test: gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.1_sunos_i86pc gcc-cygwin-3.4.4 These are already outdated results for gcc-4.0.3_linux and gcc-4.1.0_linux. The tests actually pass. The next table will reflect that state. What about 'gcc-4.1.1_sunos_i86pc' ? That seems to be a total failure. (The failure is at least partially in the regression harness; the table at http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/py... doesn't even mention it. :-(
Huh? I see it there. Looks all green to me. What am I missing?
The test run from 2007-03-31 for gcc-4.1.1_sunos_i86pc is indeed all green, even though the test report from the same date reports lots of failures. This is apparently caused by the report generator and the test runner running on different dates, so they are slightly out-of-sync. (It's the report from 2007-04-01 that contains the test runs from 2007-03-31.) Sorry for the noise. Stefan -- ...ich hab' noch einen Koffer in Berlin...
participants (4)
-
David Abrahams
-
Douglas Gregor
-
Martin Wille
-
Stefan Seefeld