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

rename fast_dev_run -> unit_test #1087

Closed
wants to merge 21 commits into from
Closed

rename fast_dev_run -> unit_test #1087

wants to merge 21 commits into from

Conversation

Gokkulnath
Copy link

@Gokkulnath Gokkulnath commented Mar 7, 2020

Before submitting

  • Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
  • Did you read the contributor guideline, Pull Request section? Yes
  • Did you make sure to update the docs? Yes
  • Did you write any new necessary tests? Not Applicable
  • If you made a notable change (that affects users), did you update the CHANGELOG? I can update if required. It is a minor change.

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 🙃

@pep8speaks
Copy link

pep8speaks commented Mar 7, 2020

Hello @Gokkulnath! Thanks for updating this PR.

Line 26:111: E501 line too long (115 > 110 characters)

Comment last updated at 2020-03-24 19:12:00 UTC

@Borda Borda added this to the 0.7.2 milestone Mar 7, 2020
@Borda Borda added the feature Is an improvement or enhancement label Mar 7, 2020
@Borda
Copy link
Member

Borda commented Mar 11, 2020

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 🤖

Copy link
Member

@Borda Borda left a 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:

pytorch_lightning/trainer/__init__.py Outdated Show resolved Hide resolved
@Borda
Copy link
Member

Borda commented Mar 19, 2020

@Gokkulnath mind rebase and check the comments above? :]

@Gokkulnath
Copy link
Author

Gokkulnath commented Mar 21, 2020

@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

@williamFalcon
Copy link
Contributor

@Gokkulnath the rename is good. But this PR also needs to add a run through a test batch to be complete.

tests/test_deprecated.py Outdated Show resolved Hide resolved
@codecov
Copy link

codecov bot commented Mar 21, 2020

Codecov Report

Merging #1087 into master will increase coverage by 0%.
The diff coverage is 96%.

@@          Coverage Diff           @@
##           master   #1087   +/-   ##
======================================
  Coverage      91%     91%           
======================================
  Files          61      61           
  Lines        3153    3161    +8     
======================================
+ Hits         2880    2891   +11     
+ Misses        273     270    -3     

@Gokkulnath
Copy link
Author

@Borda I think the PR is ready for review. Kindly let me know if any more changes are required.

Copy link
Member

@Borda Borda left a comment

Choose a reason for hiding this comment

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

almost there :]

pytorch_lightning/trainer/evaluation_loop.py Outdated Show resolved Hide resolved
pytorch_lightning/trainer/trainer.py Show resolved Hide resolved
pytorch_lightning/trainer/trainer.py Outdated Show resolved Hide resolved
pytorch_lightning/trainer/trainer.py Outdated Show resolved Hide resolved
pytorch_lightning/trainer/trainer.py Outdated Show resolved Hide resolved
pytorch_lightning/trainer/training_loop.py Outdated Show resolved Hide resolved
tests/test_deprecated.py Outdated Show resolved Hide resolved
Copy link
Member

@Borda Borda left a comment

Choose a reason for hiding this comment

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

LGTM 🚀

@Borda
Copy link
Member

Borda commented Mar 25, 2020

FYI, just opens an issue on Trains clearml/clearml#119

@Borda Borda added the ready PRs ready to be merged label Mar 25, 2020
@Borda Borda requested review from ethanwharris, jeremyjordan and a team March 25, 2020 14:38
Copy link
Contributor

@tullie tullie left a 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?

@williamFalcon
Copy link
Contributor

williamFalcon commented Mar 25, 2020

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

@Borda
Copy link
Member

Borda commented Mar 25, 2020

yeah, the Unit-test from sys eng. makes it a bit confusing... so what about dry_run?
@tullie @williamFalcon ^^

@ethanjperez
Copy link

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?

@Borda
Copy link
Member

Borda commented Mar 25, 2020

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 simple-run?

@jeremyjordan
Copy link
Contributor

in my opinion, fast_dev_run is more informative - what's the motivation to change this?

@Borda Borda added discussion In a discussion stage and removed ready PRs ready to be merged labels Mar 26, 2020
@ethanwharris
Copy link
Member

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

@Borda
Copy link
Member

Borda commented Mar 26, 2020

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 unit_test is soft.develop and fast_dev_run is not very descriptive

@Gokkulnath
Copy link
Author

What about quick_test_pipelines? Inspired from quickly leak testing the whole pipeline.

@tullie
Copy link
Contributor

tullie commented Mar 26, 2020

My favorite suggestion is probably debug-run but not totally convinced. What about “single_batch_run”?

@jeremyjordan
Copy link
Contributor

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 fast_dev_run? in other words, what are we failing to communicate in that name? to me it's pretty clear, "oh we just want to do a quick run during development to make sure everything works"

@mergify
Copy link
Contributor

mergify bot commented Mar 27, 2020

This pull request is now in conflict... :(

@Borda
Copy link
Member

Borda commented Mar 27, 2020

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 fast_dev_run? in other words, what are we failing to communicate in that name? to me it's pretty clear, "oh we just want to do a quick run during development to make sure everything works"

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 Borda self-requested a review March 27, 2020 07:15
@Gokkulnath
Copy link
Author

@Borda No problem 👍

@Borda
Copy link
Member

Borda commented Mar 30, 2020

@PyTorchLightning/core-contributors are continuing in this renaming

@mergify mergify bot requested a review from a team March 30, 2020 22:33
@williamFalcon
Copy link
Contributor

@Gokkulnath thanks for the contribution! this is my fault for not having arrived at a better name early haha. Please continute to contribute :)

@Borda Borda modified the milestones: v0.7., v0.7.x Apr 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion In a discussion stage feature Is an improvement or enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fast_dev_run -> unit_test
9 participants