)]}'
{
  "commit": "eb784d09e9490d4e21618d9eddaa4b75e1e20d59",
  "tree": "99cf226b16a354c324add08413d64386a4a2fd50",
  "parents": [
    "fa1f0a838276d6393402e642f10f1701b68239cc"
  ],
  "author": {
    "name": "fangshiwei",
    "email": "fangshiwei@xiaomi.com",
    "time": "Fri Jan 17 14:39:48 2020 +0800"
  },
  "committer": {
    "name": "Rubin Xu",
    "email": "rubinxu@google.com",
    "time": "Mon May 11 10:15:59 2020 +0000"
  },
  "message": "RESTRICT AUTOMERGE:Make sure that the LockTaskUtilityActivityIfWhitelisted was started\n\nTest:\nrun cts -m CtsDevicePolicyManagerTestCases -t com.android.cts.devicepolicy.DeviceOwnerTest#testLockTaskAfterReboot_tryOpeningSettings_deviceOwnerUser\n\nRoot cause: When preparing to start LockTaskUtilityActivityIfWhitelisted, case starts android.settings.SETTINGS through the adb command first, resulting in LockTaskUtilityActivityIfWhitelisted not starting. We should wait for LockTaskUtilityActivityIfWhitelisted started to continue the following test.\n\nBug:147858236\nChange-Id: I74a0c9b60e447f68733b77a2191e679eb62ba4c6\nMerged-In: I6db66d7de561f031ccd79738224f2cd4b9a05e34\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "99b97bdd908e7da2b6ce6ec58abf76e24fc853d5",
      "old_mode": 33188,
      "old_path": "hostsidetests/devicepolicy/app/DeviceOwner/src/com/android/cts/deviceowner/LockTaskHostDrivenTest.java",
      "new_id": "84dc6d63991bcbed19bd8ffba5bc9202e0b6a441",
      "new_mode": 33188,
      "new_path": "hostsidetests/devicepolicy/app/DeviceOwner/src/com/android/cts/deviceowner/LockTaskHostDrivenTest.java"
    },
    {
      "type": "modify",
      "old_id": "09c7a4cbb4bca10ea2401a83137e90354c1857d3",
      "old_mode": 33188,
      "old_path": "hostsidetests/devicepolicy/src/com/android/cts/devicepolicy/DeviceOwnerTest.java",
      "new_id": "2b324e7624c07c2e67e8ee7e06c16c6dda0f7692",
      "new_mode": 33188,
      "new_path": "hostsidetests/devicepolicy/src/com/android/cts/devicepolicy/DeviceOwnerTest.java"
    }
  ]
}