Since we know the library isn't going to work on any of the currently tested platforms, checking the test results seems pointless. There are a lot of failures, but if they're down to atomic not being ready, then I guess they're acceptable? I'd normally suggest marking up the failing test results in status/explicit-failures-markup.xml, but that might be counter-productive if they could be fixed in atomic. Failures due to boost dependencies are a real pain. for the mingw/interprocess related failures, i might need some help: there is a linking failure, but i don't know what to link to.
I have no idea. Maybe you could request help from Ion.
There is a test that is failing on all the Windows testers spsc_queue_test. Have you an idea of what is going wrong?
have fixed this ... seems that windows doesn't like stack-allocation of larger objects ... tim