)]}'
{
  "commit": "4f66640288dc1b5870971c8e75813f10731799ef",
  "tree": "84186f20b1f714342a119d7ec812009cbebbca5d",
  "parents": [
    "10eac86cf71af75fdcad1291543873e38fb6edaa"
  ],
  "author": {
    "name": "Ryan Harrison",
    "email": "rharrison@chromium.org",
    "time": "Tue Jun 09 15:11:01 2026 -0700"
  },
  "committer": {
    "name": "dawn-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "email": "dawn-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Tue Jun 09 15:11:01 2026 -0700"
  },
  "message": "[fuzz] Suppress specific UBSAN warning for libFuzzer itself\n\nThe specific issue is in ForEachNonZeroByte from\nthird_party/libFuzzer/src/FuzzerTracePC.h, which does have\nATTRIBUTE_NO_SANITIZE_ALL annotation on it, but that doesn cover UBSAN\nchecks.\n\nReading the libFuzzer code, there is no generic way to suppress the\nUBSAN checks in it, unlike ASAN, MSAN, and TSAN. Additionally the\nspecific problematic code is like a half decade old at a minimum, so\nthis isn\u0027t a new issue. I am assuming that either something in our\ncompiler stack or UBSAN changed, which is why this is now surfacing.\n\nnon-UBSAN sanitizers are entirely suppressed for the code in question,\nso disabling the failing check from UBSAN, since we are not going to\npatch this locally.\n\nFixes: 521747706\nChange-Id: Ie84812a780aa7c66a30ccfab57422cccef407187\nReviewed-on: https://dawn-review.googlesource.com/c/dawn/+/315275\nAuto-Submit: Ryan Harrison \u003crharrison@chromium.org\u003e\nReviewed-by: James Price \u003cjrprice@google.com\u003e\nCommit-Queue: James Price \u003cjrprice@google.com\u003e\nReviewed-by: dan sinclair \u003cdsinclair@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4882d6586bca55aba77788087d9371ad649501f3",
      "old_mode": 33188,
      "old_path": "third_party/libFuzzer/BUILD.gn",
      "new_id": "fc5e86ec8f3410d1fd7ff7a1065eb4431c2490f2",
      "new_mode": 33188,
      "new_path": "third_party/libFuzzer/BUILD.gn"
    }
  ]
}