On 10/4/15 11:35 AM, John Maddock wrote:
I can't speak for you, but I nearly always find issues in the online testing matrix that are simply not exposed by local testing (and for the record I test locally with MSVC (various versions), GCC (various versions), Intel, clang, and Oracle). Perhaps if I had local access to hardware that wasn't Intel based that might change.... but then I'd be running my own testing matrix!
Hmmm - I DO run my own testing matrix made with library_status. It's much simpler than the official one and doesn't require python or anything else. Just need to compile b2, process_jam_log and library_test. very simple, I run it everytime a make any kind of change. It almost always fails somewhere - the serialization library has a lot of tests - but it's easy to fix. And with CLang/Xcode - (which I use CMake/CTest) it's very, very fast - a few seconds for all the serialization library tests. GCC is slower, but still fine.
John.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost