)]}'
{
  "commit": "b0cc5923bf0b0315fa181542c765bfa8b8083cad",
  "tree": "e603f603debced1bdff10f3aed90d8d33456fe20",
  "parents": [
    "73c4f79b14492a930903f15553969a4e7ecbefed"
  ],
  "author": {
    "name": "Nicolas Geoffray",
    "email": "ngeoffray@google.com",
    "time": "Tue Sep 28 15:27:55 2021 +0100"
  },
  "committer": {
    "name": "Nicolas Geoffray",
    "email": "ngeoffray@google.com",
    "time": "Mon Oct 11 07:22:31 2021 +0000"
  },
  "message": "With mainline, classes in the boot classpath that hard fail can happen.\n\nSpotted while reviewing code on verifier.\n\nThis is to not abort the runtime for a scenario like:\nNew code in T, not executed in S (but still shipping on S through a\nmainline update), relies on the fact a class that was present in S\nmoved from \u0027final\u0027 to \u0027non-final\u0027. When verifying on S, this could\nlead to hard failures. But given the class is not supposed to execute,\nthat\u0027s OK.\n\nTest: device booting\nChange-Id: I68512858e9085dd45c4f9b77ac3f9dea788d3fa4\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "76cfb5e2429ddc00e8152c0c3f13287f1e6421d8",
      "old_mode": 33188,
      "old_path": "runtime/jit/jit.cc",
      "new_id": "bb421e6b20bf8f0a8a1243529b949b7bd9c5a4f5",
      "new_mode": 33188,
      "new_path": "runtime/jit/jit.cc"
    }
  ]
}