)]}'
{
  "commit": "76f829f359dfc60ed40ad988e5ead10960171361",
  "tree": "73472fec287617f6230b9b87c4a7a6047ac880a4",
  "parents": [
    "755cd4bcd48adf752bd8c161454e53a0f5b6a2fa"
  ],
  "author": {
    "name": "Googler",
    "email": "noreply@google.com",
    "time": "Tue Jul 18 08:14:53 2023 -0700"
  },
  "committer": {
    "name": "Yun Peng",
    "email": "pcloudy@google.com",
    "time": "Thu Jul 20 09:48:22 2023 +0200"
  },
  "message": "Print timestamp at the start of test execution.\n\nThe intent is to simplify debugging of timeouts and pre-test latency: this way for timeouts there will be a clear measured interval between `Executing tests...` to `Test timed out at...` lines.\n\nOne side-effect of this will be to guarantee all test logs are unique, rather than just the ones that contain a timestamped log entry or timeout. I don\u0027t expect this to be an issue, as the vast majority of logs should already be unique for some reason or another.\n\nRELNOTES: Print timestamp at the start of test execution logs.\nPiperOrigin-RevId: 549006113\nChange-Id: Iae7441a60bd7f6cbca8e96369618a44f68273039\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8529a88535ea61e8c309140d1d18fe09aca48227",
      "old_mode": 33261,
      "old_path": "tools/test/test-setup.sh",
      "new_id": "049bcef52aac8212e4486c23fe4794120737f967",
      "new_mode": 33261,
      "new_path": "tools/test/test-setup.sh"
    }
  ]
}