The transactionLifetimeLimitSeconds server parameter indicates how long a transaction may run for before it is aborted by a background thread. For tests, we set it to an extremely high value.

However, fixtures started by tests in the noPassthrough suite have the default value of 60 seconds. This seems strange though, since it means that each test which uses transactions is responsible for setting the parameter manually. It's easy to forget to this (like in this test).

I think the test fixtures should be modified so that this flag is set to a higher value (or at least, the test linked to above should use the higher value).