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

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


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

android-nexus6

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

===== 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@428610  18.6941  0.107032  18  good
chromium@428611  18.6629  0.11903   20  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 661481

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.top_25_smooth
Test Metric: frame_times/frame_times
Relative Change: 0.21%
Score: 0

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


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

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

Assigned to smoothness.gpu_rasterization.top_25_smooth owner vmiura@ to decide if this is actionable.

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

The original bisect range was too narrow due to noisy data.  Looking at individual pages it looks like the regression looks like was at the prior time point, so re-running a bisect.

This regression recovered in range 432357-432426, so if there's no success from the bisect we can close.

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.top_25_smooth
  Metric       : frame_times/ESPN


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 --story-filter=ESPN smoothness.gpu_rasterization.top_25_smooth

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

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


| 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 Speed>Bisection.  Thank you!

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

This regression looks fully recovered.  Closing.