Skip to content

Conversation

@Borda
Copy link
Collaborator

@Borda Borda commented Feb 9, 2021

What does this PR do?

for some reason there were acc tested as loss for Boring models which does not make any sense and also leads to random failers...

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
  • Check that target branch and milestone match!

Did you have fun?

Make sure you had fun coding 🙃

@Borda Borda added the ci Continuous Integration label Feb 9, 2021
@Borda Borda added this to the 1.2 milestone Feb 9, 2021
@codecov
Copy link

codecov bot commented Feb 9, 2021

Codecov Report

Merging #5876 (08d3b12) into master (ebabe56) will decrease coverage by 0%.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #5876   +/-   ##
======================================
- Coverage      93%     93%   -0%     
======================================
  Files         160     160           
  Lines       11435   11435           
======================================
- Hits        10690   10683    -7     
- Misses        745     752    +7     

@Borda Borda changed the title fixing miss-leading tested acc values [blocked by #5507] fixing miss-leading tested acc values Feb 10, 2021
Base automatically changed from release/1.2-dev to master February 11, 2021 14:32
@Borda Borda force-pushed the tests/fix-acc branch 2 times, most recently from e1241dd to 859be86 Compare February 11, 2021 17:55
@Borda Borda changed the title [blocked by #5507] fixing miss-leading tested acc values fixing miss-leading tested acc values Feb 11, 2021
@Borda
Copy link
Collaborator Author

Borda commented Feb 16, 2021

@rohitgr7 mind checks why these tests are failing, not sure how it happens that the predictions are negative...

@rohitgr7
Copy link
Contributor

@Borda can we do it separately for accelerators and trainer since only those two modules are left? After that, we can remove the unused code (related to EvalModelTemplate) once everything is done. Will try to get some time by this weekend and complete them. Can we close this for now?

@Borda Borda force-pushed the tests/fix-acc branch 2 times, most recently from 3094220 to ccb44ab Compare February 18, 2021 18:37
@Borda Borda modified the milestones: 1.2, 1.2.x Feb 18, 2021
@Borda Borda marked this pull request as ready for review February 19, 2021 20:05
@rohitgr7 rohitgr7 disabled auto-merge February 23, 2021 18:46
@mergify mergify bot removed the has conflicts label Feb 23, 2021
@rohitgr7
Copy link
Contributor

rohitgr7 commented Feb 23, 2021

getting this error here:

RuntimeError: CUDA error: all CUDA-capable devices are busy or unavailable

aren't all the jobs on azure running independently?? @Borda
or something else is causing this error?

@Borda
Copy link
Collaborator Author

Borda commented Feb 23, 2021

aren't all the jobs on azure running independently?

yes it should, each shall use own machine

@rohitgr7
Copy link
Contributor

pls do a re-review. Changed/Updated a few things here.

@Borda Borda enabled auto-merge (squash) February 23, 2021 21:40
@Borda
Copy link
Collaborator Author

Borda commented Feb 23, 2021

pls do a re-review. Changed/Updated a few things here.

GREAT, Thank you!

@Borda Borda merged commit 1c851b8 into master Feb 23, 2021
@Borda Borda deleted the tests/fix-acc branch February 23, 2021 22:08
ananthsub pushed a commit to ananthsub/pytorch-lightning that referenced this pull request Feb 24, 2021
* fixing tested values

* .

* tests

* yapf

* softmax

* hvd

* rename

* lr

* duplicate

* drop

* classif

* rm EvalModel

* Revert "rm EvalModel"

This reverts commit 6c3fb39.

* update tests

* fix

* azure

* azure

* self

* cpu

* Apply suggestions from code review

Co-authored-by: rohitgr7 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci Continuous Integration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants