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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICguc-ltAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgudD6ugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-fLJqAkM


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

chromium-rel-mac-retina
chromium-rel-win7-gpu-intel
win-zenbook

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/484
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

Annie, I wanted to re-kick the bisect for this bug but when I go to the group_report I don't see any graphs, and the original alerts link doesn't show any reference to top_10_mobile. Any idea what might be going on?

If you click "Original alerts at time of bug-filing" you'll see they're now linked to  bug 648599 .