Boost logo

Boost :

From: Douglas Gregor (gregod_at_[hidden])
Date: 2002-08-05 18:19:40


On Monday 05 August 2002 06:46 pm, Beman Dawes wrote:
> It would be easy for the program that generates the Status Reporting to
> look in a file for a list of test/compiler/version[/platform] combinations
> that need to be reported with some special status. The file could live in
> CVS, so developers can maintain it for their own tests. IOW, it wouldn't
> be the responsibility of the people who run the regression tests to figure
> out when it applied.
>
> Brainstorming a bit, let's say this is called the broken-compiler file. If
> test/compiler/version[/platform] names match the current cell, it will be
> reported as "Broken" or similar, with a link to a description that says
> something like:
>
> "This compiler fails to comply with the C++ standard in some aspect
> required to pass this test. The developer knows of no practical
> workaround. Complain to the compiler vendor!"
>
> Is that what you had in mind?

Yes, that's what I had in mind. Perhaps in the .cpp file containing the test
we could have lines like this:

// XFAIL toolsetname1
// XFAIL toolsetname2
// ...

The toolset name for each test is already available in the program that
generates the status reports, right?

        Doug


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk