On Wed, Sep 18, 2013 at 6:21 AM, Vicente J. Botet Escriba <vicente.botet@wanadoo.fr> wrote:

Hi,

The following tester fails without reporting any reason

Test output: teeks99-03d-win2008-64on64 - thread - async__async_p / msvc-11.0

Rev 85733 / Tue, 17 Sep 2013 21:09:04 +0000

Lib [2013-09-18 05:35:13 UTC]: fail

See boost/bin.v2/libs/thread/build/msvc-11.0/debug/threading-multi

Following the link

Test output: boost/bin.v2/libs/thread/build/msvc-11.0/debug/threading-multi

Rev 85733 / Tue, 17 Sep 2013 21:09:04 +0000

Compile [2013-09-18 05:35:13 UTC]: succeed

    call "C:\Program Files (x86)\microsoft visual studio 11.0\vc\vcvarsall.bat" x86 >nul
cl /Zm800 -nologo @"C:\local\teeks99-03\d\results\boost\bin.v2\libs\thread\build\msvc-11.0\debug\threading-multi\future.obj.rsp" 

future.cpp
            

Could the failing reasons be reported? 

That is odd behavior that its not outputting the error. I don't have any further insights into it, on most of my machines everything is deleted when the test finishes, so I don't keep copies to look back at.

Did something change in future.cpp (or whatever file is complied immediately after it) in the last few days? The teeks99-03a-win2008-64on64 test (which hasn't run since sunday) isn't showing the issue yet, so that seems to imply that a) this problem doesn't affect msvc-8.0, which would surprise me because it affects 9, 10, and 11 or b) that it is something that has changed since sunday.