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

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


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

android-nexus7v2

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: No values were found while testing the reference range.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@433303  N/A   N/A      0  good
chromium@433452  N/A   N/A      0  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 667487

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=tulip2.mp4.total media.android.tough_video_cases
Test Metric: vm_shared_dirty_delta/tulip2.mp4_total
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3503
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995348299556546560


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6042458717159424

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

The metric has recovered: https://chromeperf.appspot.com/report?sid=7abab73a183c3c361ebce7ef210b7145371825584d9298f6cebdd3d025435dcc&rev=433600