Leo Simons wrote:
grmbl. It is obvious to me by now that the concurrency code can lead to
deadlocks, but after lots of testing I still haven't isolated when it
occurs. We can either spend more time debugging the code (which I'm not
really feeling like; this stuff makes my head hurt) or disable the
deadlock test.
If no-one feels like fixing the code, is it okay if I disable the test?
Fine with me. This stuff is only around for back compatibility.
Better to point them to better concurrency management utils.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
