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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgu43OvAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-9WdpgoM


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

chromium-rel-mac-retina
chromium-rel-mac11

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@434174  1.62459  1.19491  27  good
chromium@434183  1.73944  1.4739   27  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 669173

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=LinkedIn smoothness.top_25_smooth
Test Metric: first_gesture_scroll_update_latency/LinkedIn
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/1064
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994717433332316672


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

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

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

Rerunning with wider range.

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@433861  1.65296  1.04607  27  good
chromium@434233  1.66774  1.23738  27  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 669173

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=LinkedIn smoothness.top_25_smooth
Test Metric: first_gesture_scroll_update_latency/LinkedIn
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/1070
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994702751990931152


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

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

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

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


===== SUSPECTED CL(s) =====
Subject : Update ts_proxy to latest commit
Author  : nednguyen
Commit description:
  
For all the changes, see: https://github.com/WPO-Foundation/tsproxy/compare/6fae6141104d077c8ceb1136b6ddee5b98f30240...9ae7d2ff822cb7cef15bc54ff614273c99691744

The main change is "Reduced CPU impact when idle or running in bypass mode".

Bug: https://code.google.com/p/chrome-os-partner/issues/detail?id=60009

BUG=chromium:653519

Review-Url: https://codereview.chromium.org/2516973005
Commit  : 4e71cc39324b205febf5a4cfa3a089a1e2aeab74
Date    : Wed Nov 23 17:55:09 2016


===== TESTED REVISIONS =====
Revision                             Mean     Std Dev   N  Good?
chromium@434144                      1.5435   0.306232  8  good
chromium@434199                      1.82175  0.877516  8  good
chromium@434226                      1.64938  0.535623  8  good
chromium@434240                      1.64588  0.475036  8  good
chromium@434247                      1.88438  0.907624  8  good
chromium@434248                      1.525    0.481626  8  good
chromium@434248,catapult@982d024dad  1.4704   0.102709  5  good
chromium@434248,catapult@4e71cc3932  2.38925  0.971056  8  bad    <--
chromium@434249                      2.5276   0.14636   5  bad
chromium@434250                      2.554    0.138174  5  bad
chromium@434253                      2.538    0.251348  8  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 669173

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=LinkedIn smoothness.top_25_smooth
Test Metric: first_gesture_scroll_update_latency/LinkedIn
Relative Change: 63.91%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/1078
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994613950975483456


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

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