All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=766207

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=b467628ba10d4f757922162d58f2650977ac01e98b4885f2a51c20aac82141f2


Bot(s) for this bug's original alert(s):

chromium-rel-mac11-pro

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12d88f97b80000

📍 Pinpoint job completed.
https://pinpoint-dot-chromeperf.appspot.com/job/12d88f97b80000

I'm curious about this. I'm going to kick off a Pinpoint job with a wider regression range.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14f230d7b80000

📍 Pinpoint job completed.
https://pinpoint-dot-chromeperf.appspot.com/job/14f230d7b80000

WontFix.

+dtu@: note that the earlier Bisect version where bisect updated the bug with results was helpful since triaging was much faster. I could quickly mark a bug WontFix after a glance (without having to click into another link)

Oh, yep! I've since added a short summary of culprits (or "nothing found") to the bug posts. I'm also going to add the size of the regressions.