Currently, the global index cloner doesn't skip the clone phase after it steps up even if the current step is already beyond it. This is mostly harmless as it will end up doing no writes because all documents that needs to be fetched are already cloned. However, this can still cause it to start a transaction when reading the skip id collection. If the cleanup gets called while that transaction is still running, it will trigger SERVER-70247 and cause the transaction to stay alive even after the cloner finished. This will then cause the test to hang because the fixture will try to acquire MODE_X during destruction.