At 10:10 PM -0600 11/25/07, Hartmut Kaiser wrote:
Martin,
Some Wave tests do fail because of spurious thread exceptions as well (here: http://tinyurl.com/2cfbzb). I'd like to know which resource limits have been exceeded
I have no access to the platforms in question, all I can tell is that a 'boost::thread_resource_error' has been thrown.
Quite likely, the number of threads exceeded a limit imposed on the test machine. This is the same as for other Boost.Thread related failures we've seen recently from my machine.
The limit has been raised globally, so if a test does not spawn many threads then it should not fail due to this condition anymore.
The interesting piece of information here is, that the Wave tests do not spawn any additional threads. Wave links against Boost.Thread only because it uses Boost.Pool which depends on Boost.Thread synchronization primitives.
Just a note: I checked in some (minor) changes to Boost.Pool last week. I don't think they could be causing these failures, but I figured that I should speak up.... -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.