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

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


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

android-one

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

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

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

=== PERF REGRESSION ===


=== Auto-CCing suspected CL author fdoray@chromium.org ===

Hi fdoray@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


===== 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@426993  2.25275  0.0601781  8  good
chromium@426994  2.33604  0.0250104  5  bad    <--
chromium@426995  2.33365  0.0359597  5  bad
chromium@426996  2.33171  0.0282031  5  bad
chromium@426998  2.32644  0.020231   5  bad
chromium@427003  2.32272  0.0168415  5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 659046

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: 3.11%

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


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

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

Not a true regression. r426994 just improved the metric by adding trace events for SequencedWorkerPool tasks (Before r426994, CPU time was not taken into account for SWP tasks. Now it is).

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