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

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


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

android-nexus6

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

=== PERF REGRESSION ===


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

Hi scottchen@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 : MD Settings: Make links inside disabled checkbox clickable on syncSetup page
Author  : scottchen
Commit description:
  
BUG= 621903 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2563443005
Cr-Commit-Position: refs/heads/master@{#437597}
Commit  : d93ce395d082047e5b0d5d4ef038eeb3106beb22
Date    : Fri Dec 09 18:52:11 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N     Good?
chromium@437587  33.2744  2873.85  5267  good
chromium@437594  33.2122  2790.81  5231  good
chromium@437596  33.1909  2969.97  5271  good
chromium@437597  33.3441  2882.02  5243  bad    <--
chromium@437598  33.283   2956.09  5262  bad
chromium@437601  33.3063  2928.77  5255  bad
chromium@437615  33.4078  2902.94  5244  bad
chromium@437643  33.3568  2904.89  5251  bad
chromium@437698  34.4188  4383.76  5084  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 673753

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests smoothness.gpu_rasterization.tough_path_rendering_cases
Test Metric: frame_times/frame_times
Relative Change: 3.44%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2827
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993380085582542560


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

| 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/8993373235403985312

That CL seems unlikely. I kicked a new bisect on the site that regressed most.

===== 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@437447  62.6323  2394.81  1836  good
chromium@437755  67.9247  3994.61  1680  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 673753

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=https...testdrive.archive.azurewebsites.net.performance.chalkboard. smoothness.gpu_rasterization.tough_path_rendering_cases
Test Metric: frame_times/https___testdrive-archive.azurewebsites.net_performance_chalkboard_
Relative Change: 8.45%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2828
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993373235403985312


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

| 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/8990022271258242528

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

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


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : sunnyps
  Commit : 1285660590d371fedced6253c43be569c2d054ee
  Date   : Fri Dec 09 21:09:57 2016
  Subject: gpu: Thread-safe command buffer state lookup.

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_path_rendering_cases
  Metric       : frame_times/frame_times
  Change       : 2.68% | 33.5884455812 -> 34.4875893373

Revision             Result                   N
chromium@437587      33.5884 +- 0.408371      6      good
chromium@437643      33.5648 +- 0.303951      6      good
chromium@437650      33.8581 +- 0.336794      6      good
chromium@437651      34.6773 +- 0.31127       6      bad       <--
chromium@437652      34.5383 +- 0.438549      6      bad
chromium@437654      34.452 +- 0.221043       6      bad
chromium@437657      34.4915 +- 0.31545       6      bad
chromium@437671      34.6322 +- 0.688222      6      bad
chromium@437698      34.4876 +- 0.533434      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests smoothness.gpu_rasterization.tough_path_rendering_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8990022271258242528

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6026896552230912


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

Bisect didn't reproduce very well, and this wasn't followed up on. Not much we can do 8 months after the regression.