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

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


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

android-nexus5

Bisect started: https://chromeperf.appspot.com/buildbucket_job_status/9016195991622480896

@sullivan: the bisect job produced nothing usable. Any ideas what happened?

I'm not sure what caused that exception. +dtu, any ideas?

I kicked off another bisect: https://chromeperf.appspot.com/buildbucket_job_status/9016035756661173792

But I also noticed that:
1) The test has no ref build
2) The test recovered on its own, but at a different revision than the other tests in this bug recovered
3) The blink_perf.canvas regression is only on one device, the N5

We've been having a LOT of trouble with the N5s this week, I think they are hooked into a bad USB hub. But this change in results could be due to device swaps.

Okay, thanks. If it is a device issue, then the bisect should confirm that the regression was imaginary.  I'll wait for that confirmation before closing.

===== 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 Value  Std. Dev.   Num Values  Good?
chromium@384311         130.403666  1.725969    18          good
chromium@384648         130.589912  1.380696    18          bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 600786

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3583
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9016035756661173792


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

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

Yep, bisect couldn't reproduce