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

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


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

android-nexus7v2

cc test owners.

Since the bisect failed with device status check error, https://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/2926, let me run another bisect.

Results in the same error.

Moving this nonessential bug to the next milestone.

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

This issue has been moved once and is lower than Pri-1. Removing the milestone.

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

Very old bug, only one bot, no ref build results, noisy test. I think it's time to close this bug.