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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgouGpuAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgouTV8ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgwo-V4goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgouTV8goM


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

android-webview-nexus6

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : percentage_smooth/http___booking.com

Revision             Result                  N
chromium@465265      69.0096 +- 19.3291      21      good
chromium@465372      69.8124 +- 12.3563      21      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=http...booking.com smoothness.top_25_smooth

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

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


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

This one is weird, the ref vanishes at the point of the alert.  I'm inclined to suspect the ref should have moved at the same time given the bots can't find a regression.

+sullivan@ what do you make of this?

+martiniss, mikecase: Wasn't there a config mixup on the webview perfbots lately, where they ran chrome instead of webview? Since we don't have webview ref builds, and ref builds are showing up in the graph, I think this is because we fixed the glitch?

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : percentage_smooth/http___booking.com

Revision             Result                  N
chromium@465265      69.0096 +- 19.3291      21      good
chromium@465372      69.8124 +- 12.3563      21      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=http...booking.com smoothness.top_25_smooth

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

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


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

re #6

Yeah, not super familiar with current situation. But I think all the "webview" perf results from the past few weeks were really testing Chrome. Also, its not 100% fixed yet, as all of the perf devices were also flashed to non-AOSP builds of Android this past month which means, even if you specify --browser=android-webview, it won't actually test the webview being installed.

Hopefully we can get this all cleaned up next week.

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : percentage_smooth/https___plus.google.com_110031535020051778989_posts

Revision             Result                  N
chromium@465265      69.0096 +- 19.3291      21      good
chromium@465372      69.8124 +- 12.3563      21      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=https...plus.google.com.110031535020051778989.posts smoothness.top_25_smooth

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

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


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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : percentage_smooth/Docs  (1 open document tab)

Revision             Result                  N
chromium@465265      69.0096 +- 19.3291      21      good
chromium@465372      69.8124 +- 12.3563      21      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=Docs...1.open.document.tab. smoothness.top_25_smooth

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

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


| 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 alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.