The transactions_reaped_with_tickets_exhausted.js starts a transaction and then runs several collection 'drop' commands on the same database which are expected to block behind the transaction. Then, the test tries to run another operation on the transaction which it expects to block behind the collection drops and eventually time out due to the transaction expiring and being reaped. At the beginning of the test, it sets transactionLifetimeLimitSeconds to 5 seconds, so that the second operation on the transaction will eventually fail when the transaction is reaped. This timeout is low enough that sometimes the transaction will get reaped before the collection drop commands are started, causing the test to erroneously fail. We should either increase this timeout or make the test resilient to timing differences on various hosts.