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

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


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

Win 7 Perf

media.desktop - Benchmark documentation link:
  None

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/114f22e2e40000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/114f22e2e40000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16dcbcdae40000

Retrying bisect with wider range...

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/16dcbcdae40000

Getting a bisection on a wider range is still blocked on bug 894529. --> dtu@ and cc+simonhatch@ for visibility and assistance obtaining a successful bisection.

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.