)]}'
{
  "commit": "14aabfca88e5956630dc96ce06ef0c8eefd4afe5",
  "tree": "96f7c0d5b3de70bdb1d771c7706ed72b2541357e",
  "parents": [
    "8a161bff1561844fc4ecd00881d51437e42aaf49"
  ],
  "author": {
    "name": "Brandon Jones",
    "email": "bajones@chromium.org",
    "time": "Thu Nov 23 20:50:48 2023 +0000"
  },
  "committer": {
    "name": "Dawn LUCI CQ",
    "email": "dawn-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Thu Nov 23 20:50:48 2023 +0000"
  },
  "message": "Fix timestamp queries on Android\n\nIt appears that timestamps in Vulkan behave much better if they are\nwritten outside of render passes. This resolves issues seen on various\nAndroid devices where timestamps for render passes were reporting 0 or\nsuspiciously low values. It also appears to have resolved an older\nQualcomm issue regarding resolving timestamp queries.\n\nBecause the issue is resolved, also re-enables the feature on Android.\n\nFixed: chromium:1504013, dawn:1559\nChange-Id: I49769fd8bbd68b60e76f66ad80781affd8afb64f\nReviewed-on: https://dawn-review.googlesource.com/c/dawn/+/162080\nReviewed-by: Kai Ninomiya \u003ckainino@chromium.org\u003e\nReviewed-by: Austin Eng \u003cenga@chromium.org\u003e\nCommit-Queue: Brandon Jones \u003cbajones@chromium.org\u003e\nKokoro: Kokoro \u003cnoreply+kokoro@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1da153b4234260c87947191e8f3f6d8b2cfba97f",
      "old_mode": 33188,
      "old_path": "src/dawn/native/vulkan/CommandBufferVk.cpp",
      "new_id": "3391b4484dc48621c3799ddabd1e6e27b45324b7",
      "new_mode": 33188,
      "new_path": "src/dawn/native/vulkan/CommandBufferVk.cpp"
    },
    {
      "type": "modify",
      "old_id": "8f75ccc18211c75598051228d0ce2f9e482f01f2",
      "old_mode": 33188,
      "old_path": "src/dawn/native/vulkan/PhysicalDeviceVk.cpp",
      "new_id": "19a1867b60910dc0698bd4da25d0c3ff9dc753ff",
      "new_mode": 33188,
      "new_path": "src/dawn/native/vulkan/PhysicalDeviceVk.cpp"
    }
  ]
}