Boost logo

Boost Testing :

From: Jeff Garland (jeff_at_[hidden])
Date: 2006-06-12 10:15:20

Thomas Witt wrote:
> Boris,
> Boris Gubenko wrote:
>> From: Thomas Witt <witt_at_[hidden]>
>>> Let me clarify this. I am perfectly willing to accept acc patches
>>> for 1.34. That is as long they don't break anything else.
>> There are low-hanging fruits though: for example, date_time library
>> tests testfacet[_dll] fail on HP-UX for exactly same reason they fail
>> on Tru64: because of the bug in the Rogue Wave library. They are marked
>> as expected failures on Tru64 and should be marked as such on HP-UX as
>> well. I'd like to modify explicit-failures-markup.xml accordingly in
>> both CVS HEAD and RC, but I don't have write access to CVS. So, how do
>> I do it? Submit a patch for .xml file?

I've made the markup for the testfacet test cases which accounts for 2
of the 7 failures. The rest of the failures look like acc compiler
issues to me. The remaining failures basically make using any of the
more recent i/o features unavailable. I could enable the old i/o code,
which is more forgiving to compilers, but honestly I'm ready to ditch
that code in 1.35 and mark any compiler that can't deal with the new i/o
unusable. Seems like the best course is probably to just mark up the
rest of the failures and hope someone at hp looks at the remaining
compiler issues. Thoughts?


Boost-testing list run by mbergal at