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

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


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

android-webview-nexus6

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

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

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


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : speedometer
  Metric       : benchmark_duration/benchmark_duration


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 speedometer

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

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


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

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

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


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : speedometer
  Metric       : benchmark_duration/benchmark_duration


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 speedometer

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

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


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

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : speedometer
  Metric       : benchmark_duration/benchmark_duration

Revision             Result                    N
chromium@465663      1.76652 +- 0.0934675      21      good
chromium@465687      1.7622 +- 0.0637897       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 speedometer

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

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


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

Seems to be a broken bisect again. The current behavior is strange, the duration doubled and ref stopped completely. What is going on?

Looking at https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20WebView%20Perf%20%283%29/builds/3012, the ref build are no longer running. I filed a bug in  issue 715977 

For this bug, I would ignore a small regression of 1.85 minutes --> 2.05 minutes (12seconds)

martiniss, mikecase: I think this change may actually be caused by the webview bots being fixed (they had accidentally been running chrome). How could we tell?

simonhatch: can you look into the failed bisect?

#12: We can tell by the bisect data? If bisect says before & after regressions have same results, then it must be due to infra change.

Was failing device_status, latest run appears to be working. Couldn't find a bug associated with fixing the failures though.

re comment 12, 13: Yeah, all the WebView bisect issues were in recipe/infra code. Bisects use the latest version of that code always, so basically, if the issue shows up in bisect its probably a real issue. If it doesnt show up in bisect, this regression was probably caused by infra.

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

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : speedometer
  Metric       : benchmark_duration/benchmark_duration

Revision             Result                    N
chromium@465663      1.76652 +- 0.0934675      21      good
chromium@465687      1.7622 +- 0.0637897       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 speedometer

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

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


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

Recovered since then.