A new test must be written without using the resharding fixture to make sure that the drop can't happen while resharding is in progress. The reason of this is that the resharding fixture have some metadata checks performed after releasing the resharding failpoint, and, if a concurrent drop (waiting for the distlock) is running, then it will drop everything after the failpoint is released but before the checks, making the test to fail because the collection is not found.