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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-JDTvQoM


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

chromium-rel-mac-hdd

Kicked off another bisect.

Bisect re-kicked with wider revision range.

Details on the below link:
------------------------------
https://chromeperf.appspot.com/group_report?bug_id=602583

Thank you!

Yet Another Bisect: https://chromeperf.appspot.com/buildbucket_job_status/9013035155654176656

fyi: I already planned to do a local bisect of this one. I just didn't have any spare cycles yet.

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Looks like this went back up, but I can't say if it's actually a recovery or something unrelated. Any ideas?

Maybe related to  issue 581777 , a WebGL feature that was turned on/off in the tree (from the log it looks incomplete the first time). The dates match and it's now in the tree and sticks. I am inclined to close this one. Objections?

This hasn't recovered all the way, but it's pretty close.

Marking WontFix as per #8.