Test Bazel remote cache issue

[nitins17]

This is to test an internal job that makes use of Bazel remote cache but is not working as intended.

[github-actions]

I pushed these containers:

• gcr.io/tensorflow-sigs/build:73-python3.10
• gcr.io/tensorflow-sigs/build:73-python3.9
• gcr.io/tensorflow-sigs/build:73-python3.8
• gcr.io/tensorflow-sigs/build:73-python3.7

Re-apply the build and push to gcr.io for staging label to rebuild and push again. This comment will only be posted once.

[bhack]

Thanks for testing this internally I was trying to use the remote cache some months ago with a simple Github Action on this repository at #48

[nitins17]

Some context on what was being tested here: we have an internal job where a Docker image could be passed as an argument. This allows us to test the nightly test suite on different build environments. When I first ran this job with the manylinux2014 Docker image from #57, I expected one of the tests to fail but Bazel instead used the cache to mark it as passed. This was puzzling as this test had never passed before in the manylinux2014 build environment so I was confused as to how the cache was used here. Turns out this is a known issue of the Bazel remote cache, i.e, it does not pay attention to differences in the things like compiler path and although it's not clear why this happened, because the toolchain for manylinux2014 appeared to be different enough. This has been resolved by changing the value of CACHEBUSTER action environment variable when upgrading the toolchain or trying out different build environments.

Thank you @angerson @perfinion for the help in resolving this!

[bhack]

Ok thanks, It seems that your issue was only related to invalidate the cache not about remote cache misses.

[nitins17]

Yes, sorry about the confusion and the lack of context in the original comment of this PR.