On 12/07/16 06:36, Tom Kent wrote:
On Tue, Dec 6, 2016 at 10:26 AM, Andrey Semashev
wrote: On 11/16/16 15:17, Andrey Semashev wrote:
On 11/16/16 15:08, Tom Kent wrote:
On Sun, Nov 6, 2016 at 5:46 PM, Tom Kent
wrote: Sorry I didn't respond sooner, I must have missed that message on the
list.
As best I can tell, something is corrupt on the msvc-9.0 install on that VM. All the other runs on that VM (teeks99-09*) are using the same base repo to clone off of, so it isn't something in the boost filesystem. If you're looking for other msvc-9.0 results, see teeks99-08b. It *should* be the identical configuration, but appears not to have this problem.
The MSVC-15 issue is known, I believe we are waiting for a build of B2 in develop that supports msvc-15.0 - Preview 5.
I just wiped the VM and started with a fresh image, this should be better now.
Thanks, I can see the tests are turning green.
I think, the problem has returned. I'm seeing the same kind of failures on teeks99-09b-win2012R2-64on64:
http://www.boost.org/development/tests/develop/developer/out put/teeks99-09b-win2012R2-64on64-boost-bin-v2-libs-log-test- src_logger_assignable-test-msvc-9-0-dbg-adrs-mdl-64-thrd-mlt.html
Hmm, interesting. I had just added the Visual Studio 2017 RC back on to that machine, apparently that does something to break Visual Studio 2008??? I need to look into this, but now sure when I'll be able to or what I will be able to find.
So, any progress about this? Would it be possible to move unreleased compilers to a separate environment?