)]}'
{
  "commit": "5d98324022a156542b768849d4dedcde49eb67d0",
  "tree": "6840afb5da54ee0a7db46ed121158557905a9336",
  "parents": [
    "c7dc024dbe9b84610646c3bcfa97f68ef63bb659"
  ],
  "author": {
    "name": "adonovan",
    "email": "adonovan@google.com",
    "time": "Wed May 13 15:02:49 2020 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Wed May 13 15:04:05 2020 -0700"
  },
  "message": "bazel syntax: stop creating wall-time profiler spans for each function call\n\nWe have a CPU profiler now, which is more accurate in the presence of\nparallelism, as every runnable but not running thread accumulates wall\ntime even as it does nothing. (Also, I saw no sign of these spans in\nwhen running blaze query --experimental_generate_json_trace_profile deps(X)\nwhere X is a Substantial Program.)\n\nThe higher-level unit of BUILD/.bzl file execution is a more appropriate span.\n\nPiperOrigin-RevId: 311411836\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "45f9914517bc0cbd61d03cd9fdbc52bce266e469",
      "old_mode": 33188,
      "old_path": "src/main/java/com/google/devtools/build/lib/syntax/StarlarkThread.java",
      "new_id": "0f3179b99beddd250da63444e9a06661b42d4e01",
      "new_mode": 33188,
      "new_path": "src/main/java/com/google/devtools/build/lib/syntax/StarlarkThread.java"
    }
  ]
}