)]}'
{
  "commit": "be7434d044e6461e84be9184d4e021f7511b0686",
  "tree": "38573c8642b9ee8ff6e478ec1294c8451c692ae7",
  "parents": [
    "f0ba189a9d1b61e25fe64750132bc1009d906d8a"
  ],
  "author": {
    "name": "Xinhao Yuan",
    "email": "xinhaoyuan@google.com",
    "time": "Mon Aug 04 18:40:46 2025 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Mon Aug 04 18:41:37 2025 -0700"
  },
  "message": "Abort on external failures in runner mode instead of keep running.\n\nThis mainly affects the unit-test mode behavior when dealing with gtest assertion failures.\n\nThis is to prepare for persistent mode, where multiple batches run in a single runner process (inside RunnerMain()).\nAborting after failure input ensures Centipede know which batch contains the failure and triage accordingly.\n\nAs a side-effect, change a unit-mode e2e test to switch to a non-failing test because the previous test generates an external failure (gTest EXPECT failure) which would cause the runner to abort without destructing the global environment.\n\nPiperOrigin-RevId: 790977540\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "80fa06db9cddd3550e27305c0a198a3847a800fc",
      "old_mode": 33188,
      "old_path": "e2e_tests/functional_test.cc",
      "new_id": "2cf56d8fcec7296c32b4b6da30b29ba8e65612d1",
      "new_mode": 33188,
      "new_path": "e2e_tests/functional_test.cc"
    },
    {
      "type": "modify",
      "old_id": "13833cab9c2bac8cfd9f825a38c49933dd999a0c",
      "old_mode": 33188,
      "old_path": "fuzztest/internal/centipede_adaptor.cc",
      "new_id": "3497f2ce21e264a666e9f774316fd4360e0ce496",
      "new_mode": 33188,
      "new_path": "fuzztest/internal/centipede_adaptor.cc"
    }
  ]
}