=== Auto-CCing suspected CL author fdoray@chromium.org ===
Hi fdoray@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.
===== 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@426992 2.97212 0.0121816 5 good
chromium@426993 2.96586 0.0163412 5 good
chromium@426994 3.03704 0.0187683 5 bad <--
chromium@426995 3.05498 0.00898794 5 bad
Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 659042
Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.key_idle_power_cases
Test Metric: tasks_per_second_total_all/set-timeout.html (Long Idle)
Relative Change: 2.79%
Score: 99.9
Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/789
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997836767099528192
Not what you expected? We'll investigate and get back to you!
https://chromeperf.appspot.com/bad_bisect?try_job_id=6374517910274048
| 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!
Comment 1 by alexclarke@chromium.org
, Oct 25 2016