-
Notifications
You must be signed in to change notification settings - Fork 614
Moved test out of run_in_graph_and_eager_mode in triplet_test #1523
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
Conversation
You are owner of some files modified in this pull request. |
@gabrieldemarmiesse, I'm not sure why having issue related to bazel, |
If you scroll in the logs, you'll see the stacktrace. It looks like a flaky test. We should have increased the absolute and relative tolerance to |
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.
Looks good, thanks again! You've been a great help! We just need to wait for the fixes to land in the master branch.
And thanks @lc0 for the review! |
This comment has been minimized.
This comment has been minimized.
@googlebot I consent. |
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
# Conflicts: # tensorflow_addons/losses/triplet_test.py
This comment has been minimized.
This comment has been minimized.
@googlebot I consent. |
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
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 again!
…flow#1523) * Moved test out of run_in_graph_and_eager_mode in triplet_test * set tolerance Co-authored-by: gabrieldemarmiesse <[email protected]> Co-authored-by: Sean Morgan <[email protected]>
cc @gabrieldemarmiesse.