Re: [boost] question regarding assert and lightweight test

From: David Abrahams (dave_at_[hidden])
Date: 2007-11-02 14:08:13

on Fri Nov 02 2007, "Robert Ramey" <ramey-AT-rrsd.com> wrote:

> Well, that makes a lot of sense.  But when I build/test with bjam
> the tail of bjam.log looks like:
>
> gcc.archive 
> ..\..\..\bin.v2\libs\serialization\build\gcc-3.4.4\debug\link-static
> \libboost_serialization-gcc34-d-1_34_1.a
> gcc.link 
> ..\..\..\bin.v2\libs\serialization\test\test_shared_ptr_132_text_archiv
> e.test\gcc-3.4.4\debug\link-static\test_shared_ptr_132_text_archive.exe
> testing.capture-output 
> ..\..\..\bin.v2\libs\serialization\test\test_shared_ptr_1
> 32_text_archive.test\gcc-3.4.4\debug\link-static\test_shared_ptr_132_text_archiv
> e.run
> ====== BEGIN OUTPUT ======
> assertion "result.second" failed: file 
> "..\..\..\libs\serialization\src\extended
> _type_info.cpp", line 75
>
> EXIT STATUS: 34304
> ====== END OUTPUT ======
> **passed** 
> ..\..\..\bin.v2\libs\serialization\test\test_shared_ptr_132_text_arch
> ive.test\gcc-3.4.4\debug\link-static\test_shared_ptr_132_text_archive.test
> ...updated 32 targets...

This looks like a serious bug, assuming you weren't doing a parallel
build (in which case the **passed** message might belong to a
different test).

Are you using the regular windows command shell to build with a cygwin
GCC?

-- 
Dave Abrahams
Boost Consulting
http://www.boost-consulting.com