-
Notifications
You must be signed in to change notification settings - Fork 27.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Training config that worked with transformers v4.4.6.3 results in OOM error with v4.47.0 (using SFTTrainer) #35108
Comments
Hey @jjbuck, thanks for the report. Can you try to find the commit that is causing this with git bisect for example. |
@SunMarc It looks like it was commit Among other things, that commit removed If I add that back such that the line reads That said, it's not clear to me what motivated that change initially, so I don't know whether it's appropriate to simply revert that change. |
This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Please note that issues that do not follow the contributing guidelines are likely to be ignored. |
Thanks for figuring out this and sorry for the late reply ! We fixed the PR you reported here. LMK if this solves your issue ! |
System Info
Who can help?
@ArthurZucker @SunMarc @muellerz
Information
Tasks
examples
folder (such as GLUE/SQuAD, ...)Reproduction
Training with transformers==4.46.3 runs as expected. Upgrading to transformers==4.47.0 (without changing anything else) leads to an OOM error in the very first training step (see stack trace below).
Run command:
accelerate launch --config_file ./accelerate_config.yaml train.py training=path/to/training_config
Accelerate Config
Training Config
Training script
Stack trace
Expected behavior
Training should complete without errors.
The text was updated successfully, but these errors were encountered: