)]}'
{
  "commit": "27a8522640d15c385a3811b546596fae4059df3e",
  "tree": "6f8490ecd4320437ebfcf94910ca39763f3b9b4b",
  "parents": [
    "8c9c6fa07bac21ee437f89473c1163df2399df6b"
  ],
  "author": {
    "name": "Zhanyong Wan",
    "email": "wan@fuchsia.infra.roller.google.com",
    "time": "Tue Mar 11 12:29:15 2025 -0700"
  },
  "committer": {
    "name": "CQ Bot",
    "email": "fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Tue Mar 11 12:29:15 2025 -0700"
  },
  "message": "[roll] Roll third_party/googletest Clarify the polymorphic matcher concept and explain how to define a composite matcher.\n\nMany gtest users aren\u0027t aware that a polymorphic matcher is not actually a `testing::Matcher\u003c\u003e` and thus doesn\u0027t know how to describe itself. Clarify this.\n\nAlso adds a recipe on how to define a composite matcher. In particular, explain how the composite matcher can describe itself in terms of the description(s) of its sub-matcher(s).\n\nPiperOrigin-RevId: 735840759\nOriginal-Revision: 4902ea2d7c6faed89b6facee00baa34bb108fc0d\n\nRoller-URL: https://cr-buildbucket.appspot.com/build/8720667682394422225\nCQ-Do-Not-Cancel-Tryjobs: true\nChange-Id: Ie2cc3a85efedadebe979fd7cece0f3e86fbda99d\nReviewed-on: https://fuchsia-review.googlesource.com/c/drivers/rtc/nxp/pcf8563/+/1225551\nCommit-Queue: GI Roller \u003cglobal-integration-roller@fuchsia-infra.iam.gserviceaccount.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4ee4b17bf5ae1bf6cdb95693c174b8830898c00b",
      "old_mode": 57344,
      "old_path": "third_party/googletest",
      "new_id": "4902ea2d7c6faed89b6facee00baa34bb108fc0d",
      "new_mode": 57344,
      "new_path": "third_party/googletest"
    }
  ]
}
