Skip to content
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

Merged
merged 7 commits into from
Sep 8, 2021

Conversation

awaelchli
Copy link
Contributor

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

  • Was this discussed/approved via a GitHub issue? (not for typos and docs)
  • Did you read the contributor guideline, Pull Request section?
  • Did you make sure your PR does only one thing, instead of bundling different changes together?
  • Did you make sure to update the documentation with your changes? (if necessary)
  • Did you write any new necessary tests? (not for typos and docs)
  • Did you verify new and existing tests pass locally with your changes?
  • Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

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:

  • Is this pull request ready for review? (if not, please submit in draft mode)
  • Check that all items from Before submitting are resolved
  • Make sure the title is self-explanatory and the description concisely explains the PR
  • Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?

I made sure I had fun coding 🙃

@awaelchli awaelchli added this to the v1.5 milestone Sep 5, 2021
@awaelchli awaelchli added callback ci Continuous Integration and removed refactor labels Sep 5, 2021
@codecov
Copy link

codecov bot commented Sep 5, 2021

Codecov Report

Merging #9326 (9266230) into master (50198d7) will increase coverage by 4%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #9326    +/-   ##
=======================================
+ Coverage      88%     92%    +4%     
=======================================
  Files         178     178            
  Lines       14858   14910    +52     
=======================================
+ Hits        13098   13761   +663     
+ Misses       1760    1149   -611     

Copy link
Contributor

@tchaton tchaton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM !

@mergify mergify bot added the ready PRs ready to be merged label Sep 6, 2021
@mergify mergify bot added the has conflicts label Sep 6, 2021
@mergify mergify bot removed the has conflicts label Sep 6, 2021
@carmocca carmocca enabled auto-merge (squash) September 6, 2021 11:45
@carmocca carmocca merged commit 91ce0d0 into master Sep 8, 2021
@carmocca carmocca deleted the feature/dev_debugger/remove_ckpt branch September 8, 2021 00:42
@carmocca
Copy link
Contributor

carmocca commented Sep 8, 2021

There seem to be some failing tests for MacOS which have crept into master:
tests/checkpointing/test_model_checkpoint.py::test_model_checkpoint_score_and_ckpt_val_check_interval

@awaelchli
Copy link
Contributor Author

I didn't notice.
But I haven't modified this test, have I?

@carmocca
Copy link
Contributor

carmocca commented Sep 8, 2021

But I haven't modified this test, have I?

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...

@awaelchli
Copy link
Contributor Author

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.

@carmocca carmocca mentioned this pull request Sep 23, 2021
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
callback ci Continuous Integration ready PRs ready to be merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants