Boost regression notification (2005-11-30 [RC_1_33_0])

Boost regression test failures ------------------------------ Report time: 2005-11-30T14:13:09Z 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... 295 failures in 3 libraries: python (285) serialization (1) spirit (9) |python| andreas_beyer: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 args: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 auto_ptr: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 back_reference: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 ben_scott1: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 bienstman1: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 bienstman2: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 bienstman3: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 builtin_converters: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 callbacks: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 const_argument: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 crossmod_exception: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 data_members: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 defaults: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 dict: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 docstring: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 embedding: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 enum: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 exception_translator: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 extract: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 implicit: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 injected: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 iterator: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 keywords: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 list: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 long: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 map_indexing_suite: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 minimal: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 multi_arg_constructor: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 nested: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 numpy: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 object: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 opaque: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 operators: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 pearu1: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 pickle1: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 pickle2: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 pickle3: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 pickle4: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 pointer_vector: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 polymorphism: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 polymorphism2: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 polymorphism2_auto_ptr: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 properties: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 raw_ctor: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 return_arg: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 select_from_python_test: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 shared_ptr: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 slice: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 staticmethod: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 str: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 test_pointer_adoption: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 try: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 tuple: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 vector_indexing_suite: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 virtual_functions: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 wrapper_held_type: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin mingw-3_4_2 |serialization| test_shared_ptr_132_binary_archive_dll: intel-8.1-linux |spirit| switch_problem: gcc-4.0.2-linux switch_problem_debug: gcc-4.0.2-linux switch_tests_eps_default: gcc-4.0.2-linux switch_tests_eps_default_debug: gcc-4.0.2-linux switch_tests_general_def: gcc-4.0.2-linux switch_tests_general_def_debug: gcc-4.0.2-linux switch_tests_single_debug: vc-8_0 switch_tests_wo_default: gcc-4.0.2-linux switch_tests_wo_default_debug: gcc-4.0.2-linux

On 11/30/05, John Maddock <john@johnmaddock.co.uk> wrote:
295 failures in 3 libraries: python (285) serialization (1) spirit (9)
What happened? Please tell me these are spurious?
Considering the numbers were about the same yesterday, I think not. -- Caleb Epstein caleb dot epstein at gmail dot com

On Nov 30, 2005, at 2:36 PM, Caleb Epstein wrote:
On 11/30/05, John Maddock <john@johnmaddock.co.uk> wrote:
295 failures in 3 libraries: python (285) serialization (1) spirit (9)
What happened? Please tell me these are spurious?
Considering the numbers were about the same yesterday, I think not.
Those tests can take more than a day to cycle :( Doug

John Maddock wrote:
295 failures in 3 libraries: python (285) serialization (1) spirit (9)
What happened? Please tell me these are spurious?
I don't think they're spurious. All gcc versions <= 3.4.x are affected by a Boost.Python problem. Could that be related to the visibility patches? gcc 4.0.2 was added to the set of fully supported compilers, recently. There's still a strange problem that this compiler has with Spirit. Regards, m Send instant messages to your online friends http://au.messenger.yahoo.com

Martin Wille <mw8329@yahoo.com.au> writes:
John Maddock wrote:
295 failures in 3 libraries: python (285) serialization (1) spirit (9)
What happened? Please tell me these are spurious?
I don't think they're spurious. All gcc versions <= 3.4.x are affected by a Boost.Python problem. Could that be related to the visibility patches?
No, it was related to bugs in my application of a patch for type name demangling. Fixed since yesterday. -- Dave Abrahams Boost Consulting www.boost-consulting.com

"John Maddock" <john@johnmaddock.co.uk> writes:
295 failures in 3 libraries: python (285) serialization (1) spirit (9)
What happened? Please tell me these are spurious?
I think the Python errors got fixed yesterday and the tests haven't caught up yet. I built a gcc-3.3.6 locally and tested it just to make sure. -- Dave Abrahams Boost Consulting www.boost-consulting.com

David Abrahams wrote:
"John Maddock" <john@johnmaddock.co.uk> writes:
295 failures in 3 libraries: python (285) serialization (1) spirit (9)
What happened? Please tell me these are spurious?
I think the Python errors got fixed yesterday and the tests haven't caught up yet. I built a gcc-3.3.6 locally and tested it just to make sure.
The tests pass for gcc 3.4.4 now, apparently. However, I'm still getting failures for gcc 3.3.6 and gcc 3.2.3, e.g. http://tinyurl.com/dat6r . These results are only a few hours old. Regards, m Send instant messages to your online friends http://au.messenger.yahoo.com

Martin Wille <mw8329@yahoo.com.au> writes:
David Abrahams wrote:
"John Maddock" <john@johnmaddock.co.uk> writes:
295 failures in 3 libraries: python (285) serialization (1) spirit (9)
What happened? Please tell me these are spurious?
I think the Python errors got fixed yesterday and the tests haven't caught up yet. I built a gcc-3.3.6 locally and tested it just to make sure.
The tests pass for gcc 3.4.4 now, apparently. However, I'm still getting failures for gcc 3.3.6 and gcc 3.2.3, e.g. http://tinyurl.com/dat6r . These results are only a few hours old.
:( missing semicolon. Fixed now. -- Dave Abrahams Boost Consulting www.boost-consulting.com
participants (6)
-
Caleb Epstein
-
David Abrahams
-
Doug Gregor
-
Douglas Gregor
-
John Maddock
-
Martin Wille