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

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


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

android-one

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1756
Failure reason: the build has failed due to infrastructure failure.

Hmmm, it feels this is just a side effect of  issue 656947 . wdyt  alexclarke@?

Maybe :)  I think it'll be very very difficult to track this down since the graph is so noisy.  Some of the graphs have improved, some haven't.


Still lets try the bisects again one last time and if they don't find anything plausible then lets close this.
 

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

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


===== SUSPECTED CL(s) =====
Subject : Use TRACE_TASK_EXECUTION in SequencedWorkerPool.
Author  : fdoray
Commit description:
  
With this CL, SequencedWorkerPool generates an event in the "toplevel"
category when it runs a task. This is the same behavior as MessageLoop,
TaskScheduler and WorkerPool.

BUG= 611818 

Review-Url: https://chromiumcodereview.appspot.com/2429863002
Cr-Commit-Position: refs/heads/master@{#426994}
Commit  : af4072ecf86c2c8ff7ec217e4830e2c2e5964cf7
Date    : Sun Oct 23 13:41:49 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N   Good?
chromium@426900  2.97625  0.169965   14  good
chromium@426950  2.97907  0.0575007  6   good
chromium@426975  2.96783  0.0728521  6   good
chromium@426988  2.95922  0.0892088  9   good
chromium@426991  2.94922  0.0612684  6   good
chromium@426993  2.95653  0.101814   9   good
chromium@426994  3.03857  0.134809   9   bad    <--
chromium@427000  3.04024  0.0765887  9   bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 659061

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=set.timeout.html..Long.Idle. thread_times.key_idle_power_cases
Test Metric: tasks_per_second_total_all/set-timeout.html (Long Idle)
Relative Change: 2.15%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2322
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993473979604141360


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

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