[Boost-testing] Re: [patch] expected-failures-markup.xml

From: Caleb Epstein (caleb.epstein_at_[hidden])
Date: 2005-05-06 13:41:16

On 5/3/05, Caleb Epstein <caleb.epstein_at_[hidden]> wrote:

> Index: status/explicit-failures-markup.xml
> ===================================================================
> RCS file: /cvsroot/boost/boost/status/explicit-failures-markup.xml,v
> retrieving revision 1.193
> diff -u -b -r1.193 explicit-failures-markup.xml
> --- status/explicit-failures-markup.xml 1 May 2005 15:52:48 -0000       1.193
> +++ status/explicit-failures-markup.xml 3 May 2005 04:07:53 -0000
> @@ -1935,6 +1935,16 @@
>              <toolset name="gcc-2.95.3-stlport-4.5.3-linux"/>
>              <note author="Aleksey Gurtovoy" refid="29"/>
>          </mark-expected-failures>
> +
> +        <mark-expected-failures>
> +            <test name="*_lib"/>
> +            <toolset name="gcc-*-sunos"/>
> +            <note author="Caleb Epstein">
> +               SunOS does not provide static versions of -lrt or
> +               -lthread, and gcc -static refuses to link with any
> +               shared objects, so these tests don't compile.
> +            </note>
> +        </mark-expected-failures>
>      </library>

I comitted this patch several days ago, yet the *_lib tests in the
Boost.Thread library don't seem to be treated as expected failures for
gcc-3_4_3-sunos.  Did I not do this correctly?

http://tinyurl.com/6t5o7

-- 
Caleb Epstein
caleb dot epstein at gmail dot com