Bhack:

To freeze TF only can you just analyze the [cache hits missing](Probably It Is something like Debugging remote cache hits for remote execution - Bazel 4.2.0) before ad after a few of llvm updated commits?


I’m not really sure. But you could also look at the the command profile after an LLVM update: https://source.cloud.google.com/results/invocations/db44e648-2768-4e83-85fc-e63e092c880b/artifacts/ 1
Just bazel analyze-profile on that doesn’t offer any insight on cache hit rate but perhaps extracting the data with --dump=raw would.