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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwovVsAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwq_spAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgor64sQoM


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

chromium-rel-win10
chromium-rel-win7-x64-dual
linux-release

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Mustaq, can you follow up on this?

From the instructions (https://chromium.googlesource.com/chromium/src/+/master/tools/perf/docs/perf_regression_sheriffing.md):
"After your shift, please try to follow up on the bugs you filed weekly. Kick off new bisects if the previous ones failed, and if the bisect picks a likely culprit follow up to ensure the CL author addresses the problem. If you are certain that a specific CL caused a performance regression, and the author does not have an immediate plan to address the problem, please revert the CL."

The bisects filed silently w/o any notification. Restarted with repeat count = 40.

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@401755  19.9005  0.0386848  5  good
chromium@401811  19.9398  0.080721   8  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 623166

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.tough_animation_cases
Test Metric: frame_times/frame_times
Relative Change: 0.13%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/261
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007408495875970768


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

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

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@401755  19.7621  0.0448962  8  good
chromium@401811  19.7709  0.0522986  8  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 623166

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.tough_animation_cases
Test Metric: frame_times/frame_times
Relative Change: 0.01%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/296
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006393039433398976


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

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

Friendly perf-sheriff ping, could your patch have caused this regression?

The ref has regressed in mid-July, reducing the impact of the original regression. Bisecting the noisy metric further to find the culprit doesn't worth the effort anymore.