How to get action results? about bazel-buildfarm

[werkt]

That file is empty. If there were any content there, the ActionResult in the ExecuteResponse would contain either the raw content, or its digest.

The start of information you want to understand is already printed out there:

      "executionMetadata": {
        "worker": "localhost:8981",
        "queuedTimestamp": "2023-10-06T17:54:34.760Z",
        "workerStartTimestamp": "2023-10-06T17:54:34.792Z",
        "workerCompletedTimestamp": "2023-10-06T17:54:42.637Z",
        "inputFetchStartTimestamp": "2023-10-06T17:54:34.792Z",
        "inputFetchCompletedTimestamp": "2023-10-06T17:54:37.295Z",
        "executionStartTimestamp": "2023-10-06T17:54:37.298Z",
        "executionCompletedTimestamp": "2023-10-06T17:54:37.834Z",
        "outputUploadStartTimestamp": "2023-10-06T17:54:37.834Z",
        "outputUploadCompletedTimestamp": "2023-10-06T17:54:42.637Z"
      }

Line up those timestamps, and you find that your operation took 2.4s to fetch, ~500ms to execute, and 4.8s to upload outputs. If you were running this against a very recent commit, you may have been subject to a revert that @80degreeswest rolled out in #1489, and I recommend you post what version of buildfarm you're running against in general if we're to pursue performance further.

[SinOverCos]

Thanks @werkt

Is there useful debug information inside /tmp/worker/shard/operations? It seems that it gets deleted after the operation ends (which makes sense).

I'm trying to debug an action that does have a much longer gap between executionStartTimestamp and executionCompletedTimestamp when executing remotely vs. locally. I'm trying to get more debug information about that specific command.

        "executionStartTimestamp":        "2023-10-13T13:21:15.991Z",
        "executionCompletedTimestamp":    "2023-10-13T13:21:24.665Z",

• when executing locally, this libgoogle_longrunning_operations_proto-speed.jar takes closer to 500ms vs. 5s

https://pastebin.com/FG8DDu9i