Skip to content

Commit 51d4804

Browse files
cheshiretensorflower-gardener
authored andcommitted
[TF2XLA] Do not promote autoclustering on compilation failure
When the explicit compilation scope fails, the right solution is to try to compile less (or to file a bug). Suggesting autoclustering in these cases is rarely helpful. PiperOrigin-RevId: 307089449 Change-Id: I082e9303cd3cff438ab6d56beaf39179e8632cc6
1 parent 907a8e1 commit 51d4804

File tree

1 file changed

+0
-7
lines changed

1 file changed

+0
-7
lines changed

tensorflow/compiler/jit/kernels/xla_ops.cc

-7
Original file line numberDiff line numberDiff line change
@@ -358,13 +358,6 @@ void XlaLocalLaunchBase::Compute(OpKernelContext* ctx) {
358358
ctx, function_, /*has_ref_vars=*/has_ref_vars_, platform_info_,
359359
resources_, constants_, /*lazy=*/false, &client, &variables, &kernel,
360360
&executable);
361-
if (!s.ok() && (platform_info_.device_type().type_string() == DEVICE_CPU ||
362-
platform_info_.device_type().type_string() == DEVICE_GPU)) {
363-
// Suggest auto jit if the failure was with GPU or CPU.
364-
errors::AppendToMessage(&s,
365-
xla::status_macros::kPossibleAutoJitAlternative);
366-
}
367-
368361
OP_REQUIRES_OK(ctx, s);
369362
}
370363

0 commit comments

Comments
 (0)