Boost logo

Boost Testing :

From: Aleksey Gurtovoy (agurtovoy_at_[hidden])
Date: 2005-02-11 18:47:07


Jonathan Turkanis writes:
> Aleksey Gurtovoy wrote:
>> Jonathan Turkanis writes:
>
>>> Finally, the 'unresolved issues' for iostreams:
>>>
>>> http://www.meta-comm.com/engineering/boost-regression/developer/issues.h
>>> tml
>>>
>>> is inconsistent with both of the above.
>>
>> Can you please elaborate? They seem perfectly consistent to me.
>
> Yes. For example, the metacomm results for Martin Wille show
> code_converter_test failing on every platform and the "old
> fashioned" report shows it failing only on gcc-2.95 without
> STLPort. But "unresolved issues" shows it failing on exactly two of
> the seven platforms.
>
> Another apparent problem with 'unresolved issues' is that none of
> the Codewarrior 9.3 or 9.4 failures are showing up.

That's because the page only lists failures for "required" toolsets --
the ones that we (Boost developers) commit to keep in accordance with
"no regression" rule. The toolsets are enumerated in
http://cvs.sourceforge.net/viewcvs.py/boost/boost/status/explicit-failures-markup.xml
and are highlighted as bold on the library and summary report pages.

-- 
Aleksey Gurtovoy
MetaCommunications Engineering

Boost-testing list run by mbergal at meta-comm.com