The test is setting a failpoint deep in the batch write path, and waiting for a $out to hit it. However, in some cases there are other threads that write to internal collections such as config.cache.collections which will also hang on the failpoint. Though there's no obvious side effects of this, the test did not intend for that behavior.