-
Notifications
You must be signed in to change notification settings - Fork 617
Added serializability tests in all optimizers and fixed serializability bug in yogi #1728
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
Added serializability tests in all optimizers and fixed serializability bug in yogi #1728
Conversation
|
@SSaishruthi @manzilz @shreyashpatodia @PhilJd @pkan2 @junjiek @CyberZHG @lokhande-vishnu You are owners of some files modified in this pull request. |
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.
Fixes look good, tyvm for the catch and much needed tests! Would you mind using the serialization test util for the comparisons though:
https://github.com/tensorflow/addons/blob/master/tensorflow_addons/testing/serialization.py#L53
In the future we could add a specialized check_optimizer_serialization as well (not needed for this PR).
|
@seanpmorgan , I think the method you suggested is too constrained. |
|
@seanpmorgan ,Please take a look at latest commit. With the use of |
|
Hi @ashutosh1919 so the bazel tests are failing because you have to explicitly link python imports that are not in the same directory. See #1740 (just the optimizer BUILD) as a fix or we can merge master into this branch after that PR merges. |
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
|
@googlebot I consent. |
|
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
Ah, this is a bit too restrictive. Could you revert your commits using the shared serialization check please. I'll create an issue to standardize all optimizer serialization checks, but want to get the bugfix in, using your first serialization check. |
|
@seanpmorgan - I have reverted the changes. And please create a separate issue to add serailizability check for optimizers in |
seanpmorgan
left a comment
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.
LGTM thanks for the fix! #1747 created for the next steps!
…ty bug in yogi (tensorflow#1728) * Added serializability tests in all optimizers and fixed serializability bug in yogi
…ty bug in yogi (tensorflow#1728) * Added serializability tests in all optimizers and fixed serializability bug in yogi
Related to #1294 .
@gabrieldemarmiesse - Please review this one.