-
Notifications
You must be signed in to change notification settings - Fork 45
Bug fix in last checkpoint save. #460
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
base: main
Are you sure you want to change the base?
Conversation
…eat save in same step
Summary of ChangesHello @chenyushuo, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces a significant improvement to the checkpointing mechanism by preventing redundant saves of various training components within a single global step. By refactoring the checkpoint managers and implementing step-based tracking for each save type, the system now avoids unnecessary I/O operations, leading to more efficient and robust training workflows. This change streamlines the checkpointing process without altering the core functionality of what is being saved. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request effectively addresses a bug that caused repeated checkpoint saves for the same step. The refactoring introduces latest_*_save_step attributes to track saves for different components individually, which is a solid approach. The code is also made more modular by extracting saving logic into separate private methods, improving readability and maintainability. I've included a few suggestions to further enhance code clarity.
2. Add process clean up in `tearDown` for `trainer_test.py` and `synchronizer_test.py` 3. Add `ignore_errors=True` for `shutil.rmtree` 4. Rename `RayUnittestBaseAysnc` to `RayUnittestBaseAsync` 5. Bug fix in last step save 6. Apply reviews from gemini
|
/unittest-module-trainer |
|
/unittest-all |
Summary
Skipped
Tests
Github Test Reporter by CTRF 💚 |
Summary
Skipped
Tests
Github Test Reporter by CTRF 💚 |
Description
latest_*_save_stepto avoid repeat save in same step, which will fix the bug where the huggingface checkpoint may not have been saved during the final training step.TestTrainerCheckpointSavetearDownfortrainer_test.pyandsynchronizer_test.pyignore_errors=Trueforshutil.rmtreeRayUnittestBaseAysnctoRayUnittestBaseAsync.Checklist
Please check the following items before code is ready to be reviewed.