Boost logo

Boost :

From: David Abrahams (dave_at_[hidden])
Date: 2003-11-29 17:21:37

Beman Dawes <bdawes_at_[hidden]> writes:

> At 01:25 PM 11/29/2003, David Abrahams wrote:
> >
> >How do I note that certain tests are expected to fail on a particular
> >compiler?
> Here is how to use the "notes" mechanism:
> In CVS, there is a file status/notes.html which provides HTML which is
> copied to the end of compiler status reports. Add to notes.html if it
> doesn't already contain the note you want to add.
> Also in CVS, there is a file status/win32-notes-map.txt which maps
> either individual tests or all tests for a library to note numbers. (A
> similar file could be created for other platforms, but this hasn't
> been done yet.) Modify this file (it has comment explaining the
> format) to add the tests you want noted.
> If you want these notes to appear on compiler status tables you are
> running locally, add:
> --notes %BOOST_ROOT%\status\notes.html --notes-map
> %BOOST_ROOT%\status\win32-notes-map.txt
> to the compiler_status command line (assuming BOOST_ROOT is defined).

Hmm, this format:

// toolset/test-name,note-#
// toolset/*library-name,note-#

Doesn't seem to provide enough ambiguity resolution. What if we have
two tests with the same name?

Also, I'd like to be able to say, "any toolset which fails this test
gets note X". We have a few tests in the iterators library which
should get the new note "this failure is not serious and won't affect
most users; the library degrades gracefully", whenever they fail.

Dave Abrahams
Boost Consulting

Boost list run by bdawes at, gregod at, cpdaniel at, john at