)]}'
{
  "commit": "2551458aefda91484a5fb4e2ce3d4685c945dd5e",
  "tree": "49b1cdf3109ec785dbf014b2f3a94e9bb1da9f8c",
  "parents": [
    "04e62a12d8350266971402197c2a3eb708906fa8"
  ],
  "author": {
    "name": "Antonio Maiorano",
    "email": "amaiorano@google.com",
    "time": "Tue Nov 16 15:09:56 2021 +0000"
  },
  "committer": {
    "name": "Tint LUCI CQ",
    "email": "tint-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Tue Nov 16 15:09:56 2021 +0000"
  },
  "message": "fix-tests: fix when gtest outputs absolute source paths\n\nSince CMake 3.21, the Ninja generator now outputs absolute paths to\nsource files, rather than relative. These paths are what __FILE__ gets\nmapped to during compilation, and is what gtest outputs for test\nfailures. This broke fix-tests, which assumed a build-relative source\npath. This change detects when the source file path is absolute, and\nconverts it to a build-relative one.\n\nAlso, on Windows, absolute paths include the drive with a colon\ncharacter, so I added matching the colon to the regex for the path\nportion.\n\nChange-Id: I065161d65f098023376b7e479d8a24a83beb1df7\nReviewed-on: https://dawn-review.googlesource.com/c/tint/+/69440\nKokoro: Kokoro \u003cnoreply+kokoro@google.com\u003e\nReviewed-by: Ben Clayton \u003cbclayton@google.com\u003e\nCommit-Queue: Antonio Maiorano \u003camaiorano@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "bb2f18d91ee6f4b2c32e5cc9bd4b647a0926df2e",
      "old_mode": 33188,
      "old_path": "tools/src/cmd/fix-tests/main.go",
      "new_id": "fd6958ca5baa601c34d884840288eb6d19fca74e",
      "new_mode": 33188,
      "new_path": "tools/src/cmd/fix-tests/main.go"
    }
  ]
}