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

make evaluate private #1260

Merged
merged 2 commits into from
Mar 30, 2020
Merged

make evaluate private #1260

merged 2 commits into from
Mar 30, 2020

Conversation

Borda
Copy link
Member

@Borda Borda commented Mar 27, 2020

What does this PR do?

Fixes #1213 (comment)

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 🙃

@Borda Borda added the bug Something isn't working label Mar 27, 2020
@Borda Borda added this to the 0.7.2 milestone Mar 27, 2020
@Borda Borda requested review from williamFalcon and a team March 27, 2020 12:32
@codecov
Copy link

codecov bot commented Mar 27, 2020

Codecov Report

Merging #1260 into master will not change coverage by %.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #1260   +/-   ##
======================================
  Coverage      92%     92%           
======================================
  Files          61      61           
  Lines        3153    3153           
======================================
  Hits         2886    2886           
  Misses        267     267           

@Ir1d
Copy link
Contributor

Ir1d commented Mar 30, 2020

@Borda when you write Fixes xxx, the issue gets closed. I don't think this PR solves #1213 in any way

@Borda Borda deleted the private-eval branch March 30, 2020 16:43
@Borda
Copy link
Member Author

Borda commented Mar 30, 2020

@Ir1d I linked just a comment was not meant to be the fix...

@Ir1d
Copy link
Contributor

Ir1d commented Mar 30, 2020

@Borda hhh, its a Github feature. You can link to the comment, but with a fix the issue is closed.

alexeykarnachev pushed a commit to alexeykarnachev/pytorch-lightning that referenced this pull request Apr 3, 2020
* make evaluate private

* changelog
@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
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Testing in dp mode uses only one of the GPUs
3 participants