Boost Testing :
From: David Abrahams (dave_at_[hidden])
Date: 2007-02-23 10:55:36
David Abrahams <dave_at_[hidden]> writes:
> Aleksey Gurtovoy <agurtovoy_at_[hidden]> writes:
>> David Abrahams writes:
>>> as far as I can tell, we're still having this problem. What do you
>>> need from me to help fix it?
>> It would be of a great help if you could determine whether
>> the compilation of that particular test (that is,
>> "libs/algorithm/string/test/replace_test.cpp") actually does fail but
>> the compiler does not obliterate the old ".obj", or the compilation
>> succeeds but the compiler returns a non-zero exit code
>> (see http://article.gmane.org/gmane.comp.lib.boost.testing/4031).
> As far as I can tell, the compilation actually succeeds and returns a
> zero exit code. Doing a new test run now...
OK, my latest logs are up there. I have *no idea* why they are
getting that old timestamp (2007-01-13-06-25-21) but that one was
generated this morning.
I honestly can't tell what's going on.
-- Dave Abrahams Boost Consulting www.boost-consulting.com