SERVER-118522 added the possibility of using FuzzTest. Even though concurrency primitives should be deterministic, we could have a fixture with MockClockSource, that generate a sorted list of <timestamp, action> where actions could be:

• client 0 tryAcquires
• client 1 acquires with 5 ms timeout
• time advances 10 ms
• client 0 releases

And adding invariants like for example:

• We never have a client waiting in the queue with an available ticket
• We never have more clients executing than maximum tickets (assuming no resizes)

The purpose of this ticket is increase the current testing coverage by adding fuzzing into the new concurrency code used by execution control.