-
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
rename fast_dev_run -> unit_test #1087
Conversation
Hello @Gokkulnath! Thanks for updating this PR.
Comment last updated at 2020-03-24 19:12:00 UTC |
hey there, we have added GPU CI test, so could we kindly ask to rebase/merge master which will trigger these tests so we do not need to test it manually... Thx for your understanding 🤖 |
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.
Thx for taking care about this change, here are some todos to be completed:
- add deprecation warning
- add backcompatibility - https://github.com/PyTorchLightning/pytorch-lightning/blob/master/pytorch_lightning/trainer/deprecated_api.py
- add tests - https://github.com/PyTorchLightning/pytorch-lightning/blob/master/tests/test_deprecated.py
- update changelog
@Gokkulnath mind rebase and check the comments above? :] |
@Borda I am not sure why the CI testing is failing for ubuntu and MacOS can you please help me in resolving the issue ? Seems to work fine on Windows CI |
@Gokkulnath the rename is good. But this PR also needs to add a run through a test batch to be complete. |
Codecov Report
@@ Coverage Diff @@
## master #1087 +/- ##
======================================
Coverage 91% 91%
======================================
Files 61 61
Lines 3153 3161 +8
======================================
+ Hits 2880 2891 +11
+ Misses 273 270 -3 |
@Borda I think the PR is ready for review. Kindly let me know if any more changes are required. |
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.
almost there :]
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 🚀
FYI, just opens an issue on Trains clearml/clearml#119 |
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.
The PR looks good to me so going to accept. I really do wonder if there's a better name for this flag though. "unit_test" is a fairly overloaded term in software engineering and imo it is slightly different to what this is. I'd personally prefer "batch_test_run" or similar. @williamFalcon how sold are you on the naming?
not sold at all. just wanted to have something that people “get” from looking at the name. but agree that unit_test is overloaded. @ethanjperez |
yeah, the Unit-test from sys eng. makes it a bit confusing... so what about |
dry-run sounds good, but makes it sound to me like you won't save anything (like checkpoints), like with rsync's dry-run. Maybe --debug-run? |
so what about |
in my opinion, |
I'm with @jeremyjordan and @tullie on this. Unit_test to me implies testing some small unit of code rather than quickly leak testing the whole pipeline. Can't think of a good suggestion for a better name though ... |
do we have any third option as |
What about quick_test_pipelines? Inspired from quickly leak testing the whole pipeline. |
My favorite suggestion is probably debug-run but not totally convinced. What about “single_batch_run”? |
there's a cost incurred when we change argument names, so i'd suggest we only do this when there's a clear improvement. what's not specific about |
This pull request is now in conflict... :( |
very much agree with @jeremyjordan, let's hold this rename until we all agree on that the new name is better than the actual one... @Gokkulnath sorry for the confusion and very much appreciate your initiative, stay with us! |
@Borda No problem 👍 |
@PyTorchLightning/core-contributors are continuing in this renaming |
@Gokkulnath thanks for the contribution! this is my fault for not having arrived at a better name early haha. Please continute to contribute :) |
Before submitting
What does this PR do?
Fixes #1081
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃