-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
remove checkpoint tracking from internal debugger #9326
Conversation
for more information, see https://pre-commit.ci
Codecov Report
@@ Coverage Diff @@
## master #9326 +/- ##
=======================================
+ Coverage 88% 92% +4%
=======================================
Files 178 178
Lines 14858 14910 +52
=======================================
+ Hits 13098 13761 +663
+ Misses 1760 1149 -611 |
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.
LGTM !
Co-authored-by: Carlos Mocholí <[email protected]>
There seem to be some failing tests for MacOS which have crept into master: |
I didn't notice. |
Doesn't look like it, but if I'm not mistaken, this is the first PR to get the failures so I can only guess it comes from one of the changes... |
They are not failing anymore on our latest runs on master: https://github.com/PyTorchLightning/pytorch-lightning/runs/3563724423 I don't know how to reproduce it or how my changes could have caused this. |
What does this PR do?
Follow up to #9188
Replaces the calls to the internal dev debugger in the model checkpoint. Tests are updated to cover what the "debugger" offered for tracking the calls inside the callback.
This is just one step towards removing the InternalDebugger completely in favor of proper unit testing.
Does your PR introduce any breaking changes? If yes, please list them.
No, the "InternalDebugger" is internal as the name suggests.
Before submitting
PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:
Did you have fun?
I made sure I had fun coding 🙃