Boost logo

Boost :

From: Misha Bergal (mbergal_at_[hidden])
Date: 2003-12-01 11:41:29

David Abrahams <dave_at_[hidden]> writes:

> Misha Bergal <mbergal_at_[hidden]> writes:
>> David Abrahams <dave_at_[hidden]> writes:
>>> How do I note that certain tests are expected to fail on a particular
>>> compiler?
>> To annotate failures in metacomm reports edit file
>> status/explicit-failures-markup.xml. I think the format is
>> self-explanatory. The mark will change the color of the fail cell from
>> red/yellow to green - the note will be displayed in the front of the
>> test related output when you follow the "fail" link.
> Can you explain what the "conf problem" text at
> means?

The process_jam_log doesn't distinguish between the tests with the
same name but different libs (for example, "list" test is in the mpl
and python libs) and assigns all "list" test results to mpl). Calling
"conf. problem" is probably wrong, but in any case if root of the
problem is fixed then it is going to go away. The same is with
"missing" test results in Boost.Python.

Misha Bergal
MetaCommunications Engineering

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