)]}'
{
  "commit": "ba00f41c0e3365e638fee70983ca10ddfbe2a2ee",
  "tree": "c9153a5ba5e32282fc631fcaf9298fb9ef553376",
  "parents": [
    "d29cb1879307a5e71b1b7fdb14207375032aefd2"
  ],
  "author": {
    "name": "Ben Clayton",
    "email": "bclayton@google.com",
    "time": "Tue Apr 16 13:23:33 2024 +0000"
  },
  "committer": {
    "name": "Dawn LUCI CQ",
    "email": "dawn-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Tue Apr 16 13:23:33 2024 +0000"
  },
  "message": "[tint][gn] Fix naming of ClusterFuzz data files\n\n`fuzzer_test.gni` doesn\u0027t handle targets that use `output_name` correctly.\n\nIt will build an executable with the requested name, but the ClusterFuzz data files (corpus, dictionary, options, owners, runtime_deps) will all use the target name for their output file names, and these will not be used by ClusterFuzz.\n\nTo work around this, if an \u0027output_name\u0027 is specified, pass the \u0027output_name\u0027 to fuzzer_test() as the target name, then make a proxy \u0027target_name\u0027 group that depends on the fuzzer target.\n\nChange-Id: I97bcc254e08f7b4d42dc1f447141c46445908f00\nReviewed-on: https://dawn-review.googlesource.com/c/dawn/+/184180\nCommit-Queue: dan sinclair \u003cdsinclair@chromium.org\u003e\nReviewed-by: dan sinclair \u003cdsinclair@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b284b4b2536e8891af8989d2aeb513aa8996749a",
      "old_mode": 33188,
      "old_path": "src/tint/tint.gni",
      "new_id": "bf48aaebfa0e1587e8ff97f76210878dcd3f1707",
      "new_mode": 33188,
      "new_path": "src/tint/tint.gni"
    }
  ]
}