diff options
author | Shanqing Cai <cais@google.com> | 2017-03-22 09:24:00 -0800 |
---|---|---|
committer | TensorFlower Gardener <gardener@tensorflow.org> | 2017-03-22 10:56:13 -0700 |
commit | 039c74293abfc8e9263ca80ab4facdde658dfb03 (patch) | |
tree | 89d862856b26b2d2941841fc4640c946272af1f1 /tensorflow/contrib/boosted_trees/proto | |
parent | b35a22c36a2500bf00d14fab16276ba75cc7af2f (diff) |
tfdbg: Let LocalCLIDebugWrapperSession error out when OpErrors happen prior to graph execution
Previously, LocalCLIDebugWrapperSession attempts to continue running and provide user with error information, instead of erroring out, even when OpError subtypes (e.g. FailedPreconditionError, InvalidArgumentError) occurred during the underlying Session.run() call. This works for errors that happen in the middle of the graph execution (e.g., most dimension mismatch errors). But if an OpError happens before any debug dump is generated, e.g., during partition graph construction due to invalid device names, LocalCLIDebugWrapperSession will mask the OpError and generate confusing error messages. The error messages complain about missing debug dump directory.
For details, see the referred GitHub issue #8507.
This CL fixes this issue by letting LocalCLIDebugWrapperSession raise the same exception as the unwrapped tf.Session does in case of this type of pre-graph execution OpErrors.
Fixes: #8507
Change: 150894042
Diffstat (limited to 'tensorflow/contrib/boosted_trees/proto')
0 files changed, 0 insertions, 0 deletions