Boost logo

Boost Testing :

From: Caleb Epstein (caleb.epstein_at_[hidden])
Date: 2005-04-20 07:57:03

On 4/19/05, Aleksey Gurtovoy <agurtovoy_at_[hidden]> wrote:
> Caleb Epstein writes:
> > I know I've asked htis before, and I'm *this* close to figuring out
> > how to do it, but I need to modify status/explicit-failures-markup.xml
> > to reflect the fact that the thread_*_lib tests are expected failures
> > on gcc + Solaris. Unfortunately, I'm not sure what to use for the
> > toolset name. Would that be gcc-*-sunos? gcc-*-solaris?
> Neither; under the current framework, you first need to rename the
> toolset to include the platform name, e.g. "gcc-sunos-3_4_3". Then,
> depending on the failure at hand, you can use either "gcc-sunos-*" or
> the exact toolset name in the markup.

I prefer gcc-3_4_3-sunos as this seems to track existing practice like
"gcc- 2.95.3- linux". I'll change my toolset name for the next run

Caleb Epstein
caleb dot epstein at gmail dot com

Boost-testing list run by mbergal at