)]}'
{
  "commit": "4c1002ad86307d5511ce9bef30b703bbf7a26816",
  "tree": "946778edbc160b0c3ed9df33e877caaa69f26b39",
  "parents": [
    "da7d0e60dd28ede70f80b18c20d9658ebf8a0f76"
  ],
  "author": {
    "name": "Chris Masone",
    "email": "cmasone@google.com",
    "time": "Mon Jun 30 16:05:03 2025 -0700"
  },
  "committer": {
    "name": "Chris Masone",
    "email": "cmasone@google.com",
    "time": "Tue Jul 01 16:02:12 2025 -0700"
  },
  "message": "[mobly] Exit non-zero on signals.TestAbortAll\n\nPer https://github.com/google/mobly/issues/960 Mobly incorrectly exits\neither 0 or 1 when a test raises signals.TestAbortAll -- depending on\nwhether any previous tests have failed or not. Instead of exiting 1 in\nthe case of all tests being aborted, like any other failure, exit with\na special code.\n\nThere aren\u0027t a lot of standard codes in use, but some internal google\ndocs suggest 40 for generic retryable errors. So use that.\n\nBug: b/425675837\nChange-Id: Iae58f6c896df2cc3d93ca9c51a84513dcd82db34\nReviewed-on: https://fuchsia-review.googlesource.com/c/third_party/github.com/google/mobly/+/1312367\nReviewed-by: Prashanth Swaminathan \u003cprashanthsw@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b32f5b0ff6ce0e7fe7a84fdb76f7b60e2fdba9b4",
      "old_mode": 33188,
      "old_path": "mobly/test_runner.py",
      "new_id": "6b4a2bcb079499c29762257db52577b1f528bd7d",
      "new_mode": 33188,
      "new_path": "mobly/test_runner.py"
    }
  ]
}