Refactor all require decorators to use skipUnless when possible #16999
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.
What does this PR do?
I was refactoring the Accelerate tests today and I noticed we use
if .. else..as a conditional for skipping tests based on imports. Unittest hasskipUnlessandskipIf, letting us simplify those decorators to be one line.E.g.:
Can be:
(Adding you as a reviewer for this Sylvain, unsure who else should be added)