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

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


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

android-nexus5X
android-one

The first bisect fails, and the second bisect is running.

kicked another bisect because the blocking issue was fixed

Moving this nonessential bug to the next milestone.

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

===== BISECT JOB RESULTS =====
Status: completed


===== TESTED REVISIONS =====
Revision                       Mean      Std Dev      N   Good?
chromium@388450                0.326237  0.0047475    12  good
chromium@388461                0.32476   0.000921503  5   good
chromium@388466                0.325597  0.00133734   8   good
chromium@388466,v8@a66ddad7aa  0.32643   0.000883783  5   good
chromium@388467                0.329673  0.000922499  5   bad
chromium@388468                0.328146  0.00207979   8   bad
chromium@388469                0.328778  0.00245506   8   bad
chromium@388471                0.328405  0.00170912   12  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 606265

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.key_idle_power_cases
Test Metric: thread_total_all_cpu_time_per_second/animated-gif.html
Relative Change: 0.05%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1337
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9010626736539208832


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

| 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!

It's v8 autoroll.

commit 37dfbe5fdd7795ef7a0cab7cf88e335a0163266e
Author: v8-autoroll <v8-autoroll@chromium.org>
Date:   Wed Apr 20 04:41:09 2016 -0700

    Update V8 to version 5.2.70.2 (cherry-pick).

    Summary of changes available at:
    https://chromium.googlesource.com/v8/v8/+log/0d3888a1..30443f81

    Please follow these instructions for assigning/CC'ing issues:
    https://github.com/v8/v8/wiki/Triaging%20issues

    Please close rolling in case of a roll revert:
    https://v8-roll.appspot.com/
    This only works with a Google account.

    TBR=hablich@chromium.org,machenbach@chromium.org,yangguo@chromium.org,vogelh
eim@chromium.org

    Review URL: https://codereview.chromium.org/1896303003

    Cr-Commit-Position: refs/heads/master@{#388467}

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 belated perf sheriff followup:

It looks like some change in https://chromium.googlesource.com/v8/v8/+log/0d3888a1..30443f81 may have affected the results of the performance test thread_times.key_idle_power_cases/thread_total_all_cpu_time_per_second/animated-gif.html.

ishell@ or jarin@, could you look at that quickly and see if there's anything that may have affected performance that we might want to spend time changing or optimizing?

Thanks :-)

This old alert is pretty insignificant given the objective perspective of time. There's little we could learn from this.