Boost Testing :
Subject: Re: [Boost-testing] Trunk testing (general) and MSVC11
From: Christoph Macheiner (christoph.macheiner_at_[hidden])
Date: 2012-08-23 13:37:49
"Beman Dawes" <bdawes_at_[hidden]> wrote in message
> On Thu, Aug 23, 2012 at 6:05 AM, Christoph Macheiner
> <christoph.macheiner_at_[hidden]> wrote:
>> - How are the MSVC testers handling crashes (of which I had several
>> this first run)? By default, the JIT-debugger kicks in with a message box
>> which is obviously not good for an unattended run.
> worked for me.
I am a little curious as to why a crash/timeout is not visible more
the status page, at least I cannot really identify any (but I am sure there
Anyway, I hope to know more after my current run is finished (and with a
luck, it is already uploaded when I am back).
>> - Is there something about not fixing things? Point in case: the CRC
>> has changes in crc.hpp (from last year) only in trunk that cause an
>> compile error on MSVC that is trivially to fix. As this header has
>> dramatically changed I cannot easily create a patch, but the author could
>> (by just looking at the code). How do I go about this? Shouldn't part of
>> development/maintenance be to try and reduce the amount of failures?
>> - 32-bit vs 64-bit. Point in case: there is a sha-1 test in UUID that is
>> only failing on 64-bit. Is there a policy regarding 64-bit tests?
> The best bet is to a posting to the main list. If the library
> maintainer is MIA, ask for some else with commit privileges to step
Okay. I skimmed through the failures of the first vc11 run, and there seemed
to be quite a few different errors (or types of errors). Does not seem to be
easy fixes as well. Otoh, I didn't expect this to be an easy task (getting
tests as possible green).