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

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

Hi reillyg@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Reilly Grant
  Commit : afe5642a20bc39ee1f3281a061b2dca851a96eb2
  Date   : Thu Jun 15 21:21:44 2017
  Subject: Temporarily move WebUSB to "experimental"

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-scavenger_avg/browse_social/browse_social_twitter
  Change       : 49.31% | 4.95550297619 -> 7.39903333333

Revision             Result                   N
chromium@479821      4.9555 +- 0.981246       6      good
chromium@479831      4.74254 +- 0.201016      6      good
chromium@479834      5.16198 +- 0.979871      6      good
chromium@479835      7.98587 +- 0.937725      6      bad       <--
chromium@479836      6.90823 +- 1.79589       6      bad
chromium@479840      8.12233 +- 0.733499      6      bad
chromium@479859      7.39903 +- 1.49175       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.twitter v8.runtimestats.browsing_mobile

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

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


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

This change has already been reverted and the graphs appear to have recovered.

 Issue 734025  has been merged into this issue.