Peter K Chan wrote:
Having done a few more runs, the test deaths seem to arise out of random
places in the execution. Sometime the test will die at one point in execution,
but pass that same point in the next execution to die at another point. This
may indicate that this is a multithreaded issue.
I will have to figure out how to isolate the problem.
Remarkable...I would never have expected this to cause a breakage, since
return jumps should be thread-specific. But I can revert that part of
the change, since it didn't help "that much" and you can let me know if
it works better.
I'd really love to have a reduced test case to show it failing, but if
it's a multithreading thing I can understand that may be difficult.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
