tree 1413ec7012bf7f14f8aa4ba464f7723de1a86d1c
parent 3c5499dcb7e938c58d1f39a7395629a9b2f4e600
author Rohan Jain <rohanj@google.com> 1635787155 -0700
committer TensorFlower Gardener <gardener@tensorflow.org> 1635787542 -0700

Fixing rpc_ops_test for when we start wrapping RPC eager ops in tf.functions. The issue was that the RPCClient op would omit returning an output in some cases which seemed to work in eager mode but when executed within a function, it complains. We ensure we return an empty string instead.

Also, marking the RpcServerRegister op as Input colocation exempt as it runs a function - ops that run functions go through the multi device backend and can handle inputs on different devices. So we don't need the placer constraint to force colocation of input resources.

PiperOrigin-RevId: 406857024
Change-Id: Id413a358244c6c42848c198023594b14806dc351