)]}'
{
  "commit": "e2b3f7e37587d1d1ecb796b9bc0fd7e2195b3677",
  "tree": "bdcba985a8e1a39eb3aa488698ef1844a15d37de",
  "parents": [
    "dd38e55468b5e05e7cdd11f28f55186fb5d2d94c",
    "529a4ecf335a35e55f433e94af6c808baa49ef44"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Sun May 10 19:05:46 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Sun May 10 19:05:46 2026 +0200"
  },
  "message": "Rollup merge of #156129 - Zalathar:pass-fail, r\u003djieyouxu\n\ncompiletest: Migrate from `PassMode`/`FailMode` to `PassFailMode`\n\nEvery UI test has an explicit or implicit “pass/fail mode” (e.g. `check-fail` or `build-pass`) that was historically stored in two separate optional fields (`pass_mode` and `fail_mode`). That split made it very hard to determine how the respective values were actually produced and consumed, especially in the presence of `--pass\u003dcheck` on the command-line, or when building auxiliary crates.\n\nThis PR replaces the separate fields and enums for pass-mode and fail-mode with a single `PassFailMode` enum and a single `pass_fail_mode` field.\n\nWith this new representation, it should hopefully be easier to understand and modify the pass/fail-mode logic.\n\n---\n\nIn order to focus on the main migration, I have mostly refrained from subsequent cleanups.\n\nr? jieyouxu\n",
  "tree_diff": []
}