-
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
pytorch 1.6 #2745
pytorch 1.6 #2745
Conversation
@yukw777 there is some issue with loading, mind have a look
|
Hello @Borda! Thanks for updating this PR. There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2020-07-30 22:48:35 UTC |
Codecov Report
@@ Coverage Diff @@
## master #2745 +/- ##
======================================
Coverage 90% 90%
======================================
Files 76 76
Lines 6768 6776 +8
======================================
+ Hits 6108 6117 +9
+ Misses 660 659 -1 |
pytorch 1.6 issue: pytorch/pytorch#42239 |
@yukw777 good job! it seems not that the update is not completely compatible with PT 1.3 mind check it? |
@tgaddair https://github.com/PyTorchLightning/pytorch-lightning/blob/8ab5bcda3d040fbe6fd616ff45793e3dfd1061ce/.github/workflows/ci-testing.yml#L104 why do we skip 3.8? can we add it back in? |
if we can, let's re-enable it in another PR :] |
Hey @yukw777, the underlying issue was fixed in Horovod 0.19.2. So provided the min version is at or above that, we can remove the checks against Python 3.8. |
@tgaddair got it, thanks! sorry for the weird location of my comment. it was late at night and i mixed up the issues lol you can delete that and post it over here if you'd like. |
No worries, comment has been moved. |
if: runner.os == 'windows' && matrix.requires == 'latest' | ||
run: | | ||
python -c "fname = 'requirements/base.txt' ; req = open(fname).read().replace('torch>=1.3', 'torch<1.5') ; open(fname, 'w').write(req)" | ||
#- name: Setup Windows on Latest |
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.
@Borda do we just want to remove this instead of commenting it out?
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.
probably at the time I commented I was not sure if it would work :]
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.
hm? so we should remove it or keep it commented like that?
@@ -309,7 +309,7 @@ def test_model_saving_loading(tmpdir): | |||
hparams_path = os.path.join(hparams_path, 'hparams.yaml') | |||
model_2 = EvalModelTemplate.load_from_checkpoint( | |||
checkpoint_path=new_weights_path, | |||
hparams_file=hparams_path | |||
hparams_file=hparams_path, |
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.
is this a good practice thing, adding a comma even after the last param?
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.
I guess black does it too as with adding new parameter dif shows changed just one line instead of two if you have to add "," to the previous one...
Co-authored-by: Peter Yu <2057325+yukw777@users.noreply.github.com>
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.
Looks good overall! I'll let you decide what to do with the commented out block in ci-testing.yml
:)
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.
👍
What does this PR do?
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 🙃