-
Notifications
You must be signed in to change notification settings - Fork 448
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
Fixing quantization in eval recipe #1777
Fixing quantization in eval recipe #1777
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/torchtune/1777
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 6242f2b with merge base 27b0fcc (): This comment was automatically generated by Dr. CI and updates every 15 minutes. |
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.
Can we add a quick test to make sure we catch the TorchTuneCheckpointerError?
Also a before (not working) / after (working) for QAT in the PR description would be great.
Which error do you mean, sorry? In this PR we raise an error if the user isn't using the correct checkpointer (i.e. TT) edit: misread, you meant a test. yep yep! |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1777 +/- ##
==========================================
- Coverage 67.38% 67.35% -0.03%
==========================================
Files 305 305
Lines 15972 15979 +7
==========================================
Hits 10762 10762
- Misses 5210 5217 +7 ☔ View full report in Codecov by Sentry. |
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.
STAMP
Context
What is the purpose of this PR? Is it to
Please link to any issues this PR addresses.
Closes #1776
On main
On this branch
Test plan
Please make sure to do each of the following if applicable to your PR. If you're unsure about any one of these just ask and we will happily help. We also have a contributing page for some guidance on contributing.
pre-commit install
)pytest tests
pytest tests -m integration_test
UX
If your function changed a public API, please add a dummy example of what the user experience will look like when calling it.
Here is a docstring example
and a tutorial example