)]}'
{
  "commit": "cb3df3bf4a9777af4e9c4337eb7318bca6d22dee",
  "tree": "ab63a2a78ace91aea177ab4962a4faf119ba2d43",
  "parents": [
    "759922d9db7183347ea4fd4be8319b8cc6f6b611"
  ],
  "author": {
    "name": "Pavel Grafov",
    "email": "pgrafov@google.com",
    "time": "Thu Mar 23 15:17:52 2017 +0000"
  },
  "committer": {
    "name": "Pavel Grafov",
    "email": "pgrafov@google.com",
    "time": "Tue Mar 28 16:37:49 2017 +0000"
  },
  "message": "Store up to 5 network log batches if needed.\n\nIn the normal mode when the DO fetches the logs ASAP, there will still be\nno more than one last full batch in memory at once. If the DO is too slow,\nor the broadcast queue is too crowded we will store up to 5 of them,\ndiscarding older ones when there are more than 5.\n\nAlso the batch gets discarded 5 minutes after it has been retrieved or\nanother more recent batch has been retrieved. Previously the last batch\nwould stay in memory until the next one is ready. But it seems\nunreasonable for the DO to rely on it since there are no guarantees.\nThis would probably even save some memory under normal conditions on\naverage.\n\nBug: 35753013\nTest: cts-tradefed run cts -m CtsDevicePolicyManagerTestCases -t com.android.cts.devicepolicy.DeviceOwnerTest#testNetworkLoggingWithSingleUser\nChange-Id: Ib8e91a98103d804375cb0d7423f93175b4b9bcb6\n(cherry picked from commit 48733074d7ba80755e40432b7ff02b66e27d3edb)\nMerged-in: Ib8e91a98103d804375cb0d7423f93175b4b9bcb6\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9b4de043a647a1876ce076b56a1de4ad871c7e71",
      "old_mode": 33188,
      "old_path": "services/devicepolicy/java/com/android/server/devicepolicy/NetworkLoggingHandler.java",
      "new_id": "70c7e586d3fee571d760f53d0827c9c326921ed2",
      "new_mode": 33188,
      "new_path": "services/devicepolicy/java/com/android/server/devicepolicy/NetworkLoggingHandler.java"
    }
  ]
}
