fsync.js expects 2 operations to be shown as "waitingForLock". However, if all tickets are exhausted, it's possible that one of the inserts will hang trying to acquire a ticket. In which case, it will never record it is waiting on a lock.

This is more likely in versions (7.0+) since execution control can dynamically reduce the number of available write/read tickets to 4.