)]}'
{
  "commit": "c0e5799fe986cac20efb05ec54f0cee03872273b",
  "tree": "8607a7c87b6a5806e15f9562f0dc0e51babf374c",
  "parents": [
    "bd81bf0df57e7877454ea20748cd6f14b1f1d5de"
  ],
  "author": {
    "name": "ulfjack",
    "email": "ulfjack@google.com",
    "time": "Fri Feb 01 14:11:46 2019 -0800"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-piper@google.com",
    "time": "Fri Feb 01 14:13:33 2019 -0800"
  },
  "message": "Always set a trap for SIGTERM in test-setup.sh\n\nIf we don\u0027t set a trap here, then bash ignores the signal, and the test\nprocess also does not receive the signal, so the test runner has no\nchance of writing a test.xml output.\n\nHowever, the behavior of trap forwarding the signal to the subprocess is\nnot at all documented in the bash documentation, and also inconsistent\nwith the behavior reported in #7119.\n\nThere is a similar problem in the Java stub template reported in #6338.\n\nThis may or may not be progress on #4608.\n\nPiperOrigin-RevId: 232035930\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "22dcb132e6c9eac0a238272d684024f34659a41c",
      "old_mode": 33261,
      "old_path": "src/test/shell/bazel/bazel_java_test.sh",
      "new_id": "a49b23c5df54e04ccf4ec3edfec5088822d470e7",
      "new_mode": 33261,
      "new_path": "src/test/shell/bazel/bazel_java_test.sh"
    },
    {
      "type": "modify",
      "old_id": "122b36c0e3e9285567600f98154208c2049478da",
      "old_mode": 33261,
      "old_path": "src/test/shell/bazel/bazel_test_test.sh",
      "new_id": "5de33479d6ab5943ddda4bcfb2b1e86d41cec3f7",
      "new_mode": 33261,
      "new_path": "src/test/shell/bazel/bazel_test_test.sh"
    },
    {
      "type": "modify",
      "old_id": "ef22b3b2a95baf7b347d48ad028e22c89a75b23b",
      "old_mode": 33261,
      "old_path": "tools/test/test-setup.sh",
      "new_id": "05a0d26223c3c82948b938e9b490bf0b2b7f01a4",
      "new_mode": 33261,
      "new_path": "tools/test/test-setup.sh"
    }
  ]
}
