Set timeout before creating pool in test #15309
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
Occasionally block_cloning_copyfilerange_fallback_same_txg fails because the clone happens in a later txg than the file creation. This can happen because the 5000 second timeout is set but we then immediately go on to the creation; there may still be a quick TXG in the pipeline that causes the clone to happen in a separate TXG.
Description
We set the timeout before creating the pool; this is what it is done in the mmp tests, which make extensive use of the txg timeout tunable. That way, all txgs are guaranteed to be long ones.
How Has This Been Tested?
ZTS runs, none of which have failed.
Types of changes
Checklist:
Signed-off-by
.