ZTS: Add slow_vdev_degraded_sit_out retry #18003
Merged
+21
−5
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
Keep the CI green. We see this occasional false positive in the CI which may distract from other real issues.
https://github.com/openzfs/zfs/actions/runs/19481983821/job/55755445615?pr=17941
I'm not thrilled about the need for this, but given that the test itself isn't entirely deterministic a retry seems like a reasonable compromise.
Description
While not common the draid3 vdev type has been observed to not always sit out a vdev when run in the CI. To prevent continued false positives allow the test to be retried up to three times before considering it a failure.
How Has This Been Tested?
Locally tested by manually injecting random percentage of failed sit outs to test to retry code.
Types of changes
Checklist:
Signed-off-by.