execution log doesn't contain remote-cacheable key

[alexeagle]

src/main/protobuf/spawn.proto contains a cacheable key, which is used to log the spawn in

bazel/src/main/java/com/google/devtools/build/lib/exec/SpawnLogContext.java

Line 140 in 329b22a

builder.setCacheable(Spawns.mayBeCached(spawn));

This allows you to filter the execution log for actions that are marked with no-cache tags (or are not cacheable due to some other condition)

However the no-remote-cache tag isn't reflected in the execution log at all.

So for example building

genrule(
    name = "large-output",
    srcs = [],
    outs = ["out"],
    cmd = "head -50104 /dev/random > $@",
    tags = ["no-remote-cache"],
)

results in execution log with only these boolean fields

  "remotable": true,
  "cacheable": true,
  "progressMessage": "Executing genrule //:large-output",
  "actualOutputs": [
    {
      "path": "bazel-out/k8-fastbuild/bin/out",
      "digest": {
        "hash": "c3df9f58fa71c57b788f3fbd224d0e3d5ebfc8cd5acc20ab752e8de2ae07885c",
        "sizeBytes": "12824891",
        "hashFunctionName": "SHA-256"
      }
    }
  ],
  "remoteCacheHit": false,

As a result, there is currently no way to find actions which produce large outputs unsuitable for remote caching, and which are not correctly tagged to avoid uploading those large outputs (more context in #11182 )