Fix endianness issues in arithmetic_optimizer_test.cc tests
Hi @ezhulenev Can you please review this PR ? Thank you! @ezhulenev, friendly ping :) Would you have some time to review this PR? Thank you! Hi @ezhulenev Can you please review this PR ? Thank you! TFTR @ezhulenev! @ezhulenev @gbaned this PR has been approved for a while now. Is there something I need to do for it to be merged? > @ezhulenev @gbaned this PR has been approved for a while now. Is there something I need to do for it to be merged?

Hi @jonathan-albrecht-ibm Sorry for the delay, this PR processing internally, nothing pending from you end. Thank you! Here are the internal errors, @jonathan-albrecht-ibm can you please verify ? Thank you!

/tensorflow/core/util/tensor_bundle/byte_swap_tensor.cc:150:56: error: no member named 'data' in 'absl::Cord'
  150 |   char* buff = const_cast<char*>((tp->tensor_content().data()));
      |                                   ~~~~~~~~~~~~~~~~~~~~ ^
1 error generated.

tensorflow/core/util/tensor_bundle/byte_swap_tensor.cc:150:56: error: no member named 'data' in 'absl::Cord'
  150 |   char* buff = const_cast<char*>((tp->tensor_content().data()));
      |                                   ~~~~~~~~~~~~~~~~~~~~ ^
1 error generated. @gbaned thanks for providing the details. Is there somewhere I can see the logs with the internal errors above?

Not completely sure what's going on but it looks like `absl::Cord` is being used instead of `std::string` for the protobuf `tensor_content` field in this build? `tensor_content` has the protobuf type `bytes` which should be `std::string` in the c++ generated classes so not sure how this is happening. 

@gbaned @ezhulenev Any pointers on how to configure my local build to reproduce this error? Hi @ezhulenev Can you please take a look on the above comment from @jonathan-albrecht-ibm. Thank you! Hi @ezhulenev Any update on this PR? Please. Thank you! @ezhulenev, @gbaned Not sure if something else changed but the MacOS build passed this time. The `Py+CPP Test Suite - Ubuntu CPU, Python 3.9` build failed though. I looked at the logs that I can access and it looks like the errors were due to timeouts IIUC.

Could someone with more access confirm? @gbaned just wanted to check on the status of this issue since the ready to pull label was removed. I don't have access to the internal CI. Are there any problems?
Some tensorflow/core/grappler/optimizers/arithmetic_optimizer_test.cc tests check for expected tensor content values that are in little-endian format. This commit adds supporting functions so that big-endian platforms will convert to little-endian before checking.