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

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


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

android-nexus7v2

===== 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@391226  20.6462  0.288472  5  good
chromium@391453  20.7642  0.30158   5  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 610245

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/2959
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013151394205594352


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

| 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 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@391226  20.7174  0.118404  6  good
chromium@391453  20.7841  0.107677  6  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 610245

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/2960
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013151399130188816


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

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

Trying a wider bisect.

===== 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@391190  20.6858  0.185194   6  good
chromium@391500  20.8218  0.0844765  6  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 610245

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/2961
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013132601452367040


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

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

+tdresser

Tim could this be the same thing as https://bugs.chromium.org/p/chromium/issues/detail?id=605839?  The graph seems to be a bit noisy after that, and I'm wondering if the alerting system got confused.

Yeah, looks like the same root cause to me.

Marking WontFix.