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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5qqqpQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5uWRqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5vyMuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5oSmqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpoeBsgsM


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

android-nexus5X
android-nexus6
chromium-rel-mac-hdd
chromium-rel-mac10
chromium-rel-win7-gpu-ati

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

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

Hi junov@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : Fixing regression in putImageData blink perf test
Author  : junov
Commit description:
  
Creating the image data object by using createImageData instead of
getImageData to avoid state changes that interfere with the
benchmark's execution.  Also doing a drive-by code simplification

BUG= 630670 

Review-Url: https://codereview.chromium.org/2190523003
Cr-Commit-Position: refs/heads/master@{#409263}
Commit  : c3a213e577d12c648fce456d2e0098fe36194abd
Date    : Tue Aug 02 19:12:45 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@409260  457.465  2.78402   5  good
chromium@409262  459.199  0.843902  5  good
chromium@409263  377.857  15.7892   5  bad    <--
chromium@409265  382.681  12.4616   5  bad
chromium@409270  385.974  9.64917   5  bad
chromium@409280  387.519  6.80375   5  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 634475

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.canvas
Test Metric: putImageData/putImageData
Relative Change: 15.29%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2271
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005226258416531584


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

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

===== 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@409255  117.593  53.7818  18  good
chromium@409324  124.486  13.2234  18  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 634475

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.canvas
Test Metric: putImageData/putImageData
Relative Change: 10.01%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/526
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004136114161433456


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

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

Regression is due to a change to the test.