Fix Trainer MLU Availability Import For Accelerate < 0.29 #32463
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?
Fixes #32461
I checked Accelerate, and the utility for checking if MLU is available was added in the
0.29.0
release, so the accelerate import in the trainer breaks versions0.21.0 >= x <0.29.0
if accelerate is available at import time (since the minimum version of accelerate transformers is happy with is 0.21.0 in the deps table).It appears that the
is_mlu_available
check in the Accelerate import utils (here) is also only used one time and is redundant with theis_torch_mlu_available
check in transformers import utils here, which is used in other parts of the trainer.This PR removes the accelerate util that is breaking the import, and just uses the transformers one in its place.
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@muellerzr and @SunMarc