Problems when doing 100 lock/release operations

[pgagne]

While evaluating ResourceLocker for the LNST team. I wrote up a test to do 100 lock operations on the same resource to test the system behavior.

My test code had a wrapper are rlock command that did the lock and release operations in N threads.

We noticed that at some point in the process, one of the signoffs would get "stuck" and have to be released manually, and the process would continue fine.

Tested with 10,20,50, 75 of the same operations and it seemed to work fine.

Its entirely possible the issue is with my multi-threaded test code.

We tried to debug this a bit, but it was a little difficult given each lock/release operation was happening in its own python thread and it was hard to follow output.

We decided that perhaps it would be easier to test debug using a native python API so we are going to work on that and come back to this at a later time.