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

wandb logger 'global_step' affects other logger #1492

Merged

Conversation

olineumann
Copy link
Contributor

@olineumann olineumann commented Apr 14, 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?
  • Did you make sure to update the docs? Not needed just a fix...
  • Did you write any new necessary tests? Probably not necessary...
  • If you made a notable change (that affects users), did you update the CHANGELOG?

Should I make an changelog update or will a maintainer do this?

What does this PR do?

Fixes #1485 .

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.

Shortly discussed in #1485 with @Borda

Did you have fun?

Yes a lot! :D

@mergify mergify bot requested a review from a team April 14, 2020 21:00
@Borda Borda added bug Something isn't working feature Is an improvement or enhancement labels Apr 14, 2020
@Borda Borda added this to the 0.7.4 milestone Apr 14, 2020
Copy link
Contributor

@awaelchli awaelchli left a comment

Choose a reason for hiding this comment

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

:)

pytorch_lightning/loggers/base.py Outdated Show resolved Hide resolved
@olineumann
Copy link
Contributor Author

The reason why the tests are failling is because the tests are checking the actual 'log' call parameters. So the tests need to be updated right? Is there something I can do or should I just wait until someone fix this and merge it in 0.7.4? :)

I didn't go through all tests, but the one I checked all displayed the same:

E           AssertionError: Expected call: log({'acc': 1.0})
E           Actual call: log({'acc': 1.0}, step=None)

@Borda Borda modified the milestones: 0.7.4, 0.7.5 Apr 24, 2020
@Borda Borda requested a review from awaelchli April 25, 2020 19:13
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.

pls add change note

@mergify mergify bot requested a review from a team April 25, 2020 19:14
@mergify mergify bot requested a review from a team April 25, 2020 20:45
@Borda Borda added the waiting on author Waiting on user action, correction, or update label Apr 26, 2020
@mergify mergify bot requested a review from a team April 28, 2020 20:41
@olineumann
Copy link
Contributor Author

pls add change note

Sorry currently I'm a little bit bussy and noticed it too late. Because 0.7.4 is over I added it to 0.7.5. Sorry...

@awaelchli
Copy link
Contributor

I can fix the test if you are busy. Thanks for the pr.

@awaelchli
Copy link
Contributor

actually no, I can't because of permissions haha. But the fix for the test is easy, just change line 19 to:

wandb.init().log.assert_called_once_with({'acc': 1.0}, step=None)

and line 23 to

wandb.init().log.assert_called_once_with({'acc': 1.0}, step=3)

@olineumann
Copy link
Contributor Author

actually no, I can't because of permissions haha. But the fix for the test is easy, just change line 19 to:

wandb.init().log.assert_called_once_with({'acc': 1.0}, step=None)

and line 23 to

wandb.init().log.assert_called_once_with({'acc': 1.0}, step=3)

Ah okay... I didn't know I can affect the CI Pipeline. I thought only contibutors can do it. Sorry. I will take care of it tomorrow.

@olineumann
Copy link
Contributor Author

Okay... It didn't let me rest so I quickly fixed it :D. On my machine, everything for wandb logger passed. Maybe one notice: I installed requirements.txt, requirements-extra.txt and tests/requirements.txt but some packages were missing yet. Did I missed one or should someone update requirements? Then someone should open an issue? I could update it in a few days after exams.

@codecov
Copy link

codecov bot commented Apr 28, 2020

Codecov Report

Merging #1492 into master will decrease coverage by 0%.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #1492   +/-   ##
======================================
- Coverage      88%     88%   -0%     
======================================
  Files          69      69           
  Lines        4133    4131    -2     
======================================
- Hits         3656    3654    -2     
  Misses        477     477           

@mergify mergify bot requested a review from a team April 28, 2020 23:19
@awaelchli
Copy link
Contributor

thanks for fixing the test. the changelog entry should be moved to the "unreleased" section.

@olineumann
Copy link
Contributor Author

thanks for fixing the test. the changelog entry should be moved to the "unreleased" section.

Done! Sorry about the mess... :/

@awaelchli
Copy link
Contributor

No problem, thanks for fixing it so promptly.

@awaelchli awaelchli requested a review from Borda April 29, 2020 09:12
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 🦝

CHANGELOG.md Outdated Show resolved Hide resolved
@Borda Borda added ready PRs ready to be merged and removed waiting on author Waiting on user action, correction, or update labels Apr 29, 2020
@Borda Borda requested review from jeremyjordan and a team April 29, 2020 10:41
@mergify
Copy link
Contributor

mergify bot commented Apr 30, 2020

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

@Borda
Copy link
Member

Borda commented Apr 30, 2020

falling on test_lbfgs_cpu_model accuracy but I do not think it is connected...

@mergify
Copy link
Contributor

mergify bot commented May 1, 2020

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

@Borda Borda force-pushed the issue/wandb_global_step branch from 30d8dc4 to fe51559 Compare May 1, 2020 19:07
@williamFalcon williamFalcon merged commit 152a2eb into Lightning-AI:master May 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working feature Is an improvement or enhancement ready PRs ready to be merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

wandb logger 'global_step' affects other logger
4 participants