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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtvDkqAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1pbOpAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1o_MoAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1qWwrAoM


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

android-nexus6

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9004795739617869088

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9004240937978537184

This is already accounted for on a macro scale. We should be able to close as wontfix at this point.

> This is already accounted for on a macro scale
Uh, what does it mean?

If I click to both links on #1 they don't show any alert/data. Is it because the alerts have been retriaged?

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

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

Obsolete perf regression alert with more than one year of inactivity.