-
Notifications
You must be signed in to change notification settings - Fork 351
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
Autograph issues #137
Comments
The output suggests that autograph can't handle calls to contract_between: It throws a warning and falls back to non-autograph tracing.
Possibly the error handling is causing overhead? Probably we can find out what's slow using PS: I think the default changed for |
Is there a way to make this a failing test? |
Yes, we can test for these log messages: https://docs.pytest.org/en/latest/logging.html |
What is the impact of this bug? Is it harmless to correctness? |
When
tf.function(autograph=True)
, the compile times for code that usescontract_between
skyrockets. This is bad becauseautograph=True
is the default fortensorflow>=1.14.0
.We need to figure out where the bug lies, either on our end or on the tensorflow end.
The text was updated successfully, but these errors were encountered: