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

Fix hparams.encoder forgotten rename in CPCv2 #773

Merged
merged 10 commits into from
Nov 26, 2021

Conversation

praecipue
Copy link
Contributor

@praecipue praecipue commented Nov 18, 2021

self.hparams.encoder was renamed to self.hparams.encoder_name in a8e3fb5 PyTorchLightning#264, but not in forward method. That leads to different errors depending on used encoder module.

CPC module test skip reason is misleading. In the meantime another errors were introduced, a workaround is for 2e903c3

What does this PR do?

Re-enable testing CPCv2
Workaround bug introduced by 2e903c3

The error is misleading, the cause is overlooked hparam rename fixed in the following commit

Fixes problem similar to #680 (#679 issue) and re-enables test

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?
  • 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?
  • Did you write any new necessary tests? [not needed for typos/docs]
  • Did you verify new and existing tests pass locally with your changes?
  • If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

  • Is this pull request ready for review? (if not, please submit in draft mode)

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 🙃

Skip reason is no longer valid. In the meantime another errors were introduced, a workaround is for 2e903c3
self.hparams.encoder was renamed to self.hparams.encoder_name in a8e3fb5 PyTorchLightning#264
Rename overlooked occurrence as in 2163626 PyTorchLightning#680
@praecipue praecipue marked this pull request as ready for review November 18, 2021 17:51
@Borda Borda added the fix fixing issues... label Nov 26, 2021
Co-authored-by: praecipue <43908213+praecipue@users.noreply.github.com>
@Borda Borda enabled auto-merge (squash) November 26, 2021 08:35
@mergify mergify bot added the ready label Nov 26, 2021
@Borda
Copy link
Member

Borda commented Nov 26, 2021

@praecipue mind check the failing GPU test? just restarted the job to see if it was related to your change... 🐰

auto-merge was automatically disabled November 26, 2021 16:07

Head branch was pushed to by a user without write access

@praecipue
Copy link
Contributor Author

@praecipue mind check the failing GPU test?

For some reason spawning DDP process was causing failure. I think it is not related to my change. Is DDP spawn tested anywhere on azure?
I've avoided the failure by using at most 1 GPU in the CPC test.

@Borda Borda merged commit ecf5376 into Lightning-Universe:master Nov 26, 2021
Borda added a commit that referenced this pull request Nov 29, 2021
* Re-enable testing CPCv2
* Fix hparams forgotten rename in CPCv2 module

Co-authored-by: Jirka Borovec <Borda@users.noreply.github.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix fixing issues... ready
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants