)]}'
{
  "commit": "c68ac4d2e2ffdf1a9ffc6ed4e90ba17bb6810ef6",
  "tree": "92feb5221fa62f73e3feed8beaa880b34ba83e1a",
  "parents": [
    "f897a092f19d7a2f84251837b00a1795dcf574d0"
  ],
  "author": {
    "name": "Suren Baghdasaryan",
    "email": "surenb@google.com",
    "time": "Thu Jul 22 16:04:18 2021 -0700"
  },
  "committer": {
    "name": "Suren Baghdasaryan",
    "email": "surenb@google.com",
    "time": "Fri Jul 23 16:13:55 2021 +0000"
  },
  "message": "Add current and max thrashing levels in LmkKillOccurred reports\n\nThrashing threshold tuning requires collecting thrashing level data from\nthe field and correlating these levels with other indications of device\nbeing non-responsive.\nInclude current and max thrashing levels in the lmkd kill reports. Max\nthrashing level captures the highest level seen since the last kill report.\n\nBug: 194433891\nSigned-off-by: Suren Baghdasaryan \u003csurenb@google.com\u003e\nChange-Id: If6dbe32a1faad55ac02a513144a535a16c09bf35\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a69c9e121a88ca49268513f5e4dca5fab49a777a",
      "old_mode": 33188,
      "old_path": "stats/atoms.proto",
      "new_id": "552d5a34965486652b4053e2839260dd74af3273",
      "new_mode": 33188,
      "new_path": "stats/atoms.proto"
    }
  ]
}