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

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


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

cros-monroe

To the current gfx guard

This is a bit fuzzy. CrOS changes in the range
https://crosland.corp.google.com/log/10522.0.0..10529.0.0

But it also includes the forced Chrome uprev with the changes that caused the graphics_Idle regressions. And Chrome has not upreved since. So it would be good to get a repro and then also check with tot Chrome.

This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.