bhack

@gunan Thanks I've intercepted this candidate dup https://github.com/tensorflow/tensorflow/issues/34719. Probably you can find some other ones on the TF repo.

If this is going to take too much time can we find an intermediate goal like having support for python only PR? I think that it could be easier as...

See what kind of bad hack I need to suggest https://github.com/tensorflow/tensorflow/pull/41701#discussion_r460587524

/cc @perfinion for @gunan post in https://groups.google.com/a/tensorflow.org/forum/m/#!topic/developers/1OJLv2ew7pA

I've tested your initial cache inside official TF Docker devel image but it has not the cross tools (d7/d8) like RBE and custom-ops Dockerfiles/images. We have a threads in SIG-build...

Also when we are mounting the bazel cache inside the official Tensorflow Docker devel container we need to improve the stale cache handling. Too often I see `Deleting stale sandbox...

In the meantime can we reply to https://groups.google.com/a/tensorflow.org/g/developers/c/1OJLv2ew7pA? Is there a quick solution to iterate and modify the source code and run an example in the source dir without building...

It seems that now we have a read only cache for TF IO but still not for Tensorflow contributors: https://github.com/tensorflow/io/pull/1294

With @angerson and @perfinion we are prototyping with https://github.com/tensorflow/tensorflow/pull/48421 (and https://github.com/tensorflow/build/pull/24) to continuously execute and monitor the external developer contribution experience/overhead (compile, lint and test). /cc @theadactyl @nikitamaia

I think we could close this and monitor the build reproducibility and cache efficiency in https://github.com/tensorflow/build/pull/48