)]}'
{
  "commit": "a72567af679408ae6789d147e63e0e208d7d65a5",
  "tree": "92c05bf66525f5e25ac490659ed4051d355bae03",
  "parents": [
    "e5759a7c24b855fdb95082dffab27a6e246913de"
  ],
  "author": {
    "name": "jmmv",
    "email": "jmmv@google.com",
    "time": "Mon Jun 08 04:01:21 2020 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Mon Jun 08 04:03:18 2020 -0700"
  },
  "message": "Prevent \"Deleting stale sandbox\" messages when things go right.\n\nMake Bazel clean up the sandbox base\u0027s top directory after the end of each\nbuild and during server shutdown to prevent this directory from staying\nbehind.\n\nThis directory is only supposed to stay behind when --sandbox_debug is\nused, and the startup message is intended to tell the user that a heavy\noperation is about to happen -- but we should not print it unnecessarily.\n\nThis was the original intent when this message was added but for some\nreason I missed this obvious case.  Added a test now.\n\nFixes #8525.\n\nRELNOTES: None.\nPiperOrigin-RevId: 315247251\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "cb96021790ec0fa05e4d091b3acfeffc5c109933",
      "old_mode": 33188,
      "old_path": "src/main/java/com/google/devtools/build/lib/sandbox/SandboxModule.java",
      "new_id": "16ce5bae2df5ebfee68d76735cf9495e5f78cb88",
      "new_mode": 33188,
      "new_path": "src/main/java/com/google/devtools/build/lib/sandbox/SandboxModule.java"
    },
    {
      "type": "modify",
      "old_id": "433df86fd8ead0168c04a175e3c29f1c95035422",
      "old_mode": 33261,
      "old_path": "src/test/shell/integration/sandboxing_test.sh",
      "new_id": "3b106c9125845097a9d34bfe3c1ef114121cfed7",
      "new_mode": 33261,
      "new_path": "src/test/shell/integration/sandboxing_test.sh"
    }
  ]
}