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


===== TESTED REVISIONS =====
Revision                Exit Code   Std. Dev.   Num Values  Good?
chromium@384558         1           N/A         20          good
chromium@384564         1           N/A         20          bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 604498

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests sunspider
Test Metric: board_temperature/board_temperature
Relative Change: 0.00%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/608
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9015008848743302096


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

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

Need to launch it again, the 'good' revision flaked (passed 19, failed one)
I'll try with a single run per rev.

Apparently not consistently failing now; there are new results at https://chromeperf.appspot.com/report?sid=b031dc0da103b34afd3007d137d18f74214bf4789095425279b46df2e41d5c97.