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

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


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

android-nexus5X

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

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

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


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_other_cpu_time_per_frame/thread_other_cpu_time_per_frame


To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.key_silk_cases

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

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


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

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

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


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_other_cpu_time_per_frame/thread_other_cpu_time_per_frame


To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.key_silk_cases

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

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


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

Set Speed>Bisection for "Bisect failed for unknown reasons"

Just an idea, but isn't it possible to set Speed>Bisection automatically when bot reports unknown failures?

+simonhatch, see #7

Yeah that's totally doable, logged an issue: https://github.com/catapult-project/catapult/issues/3594

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_other_cpu_time_per_frame/thread_other_cpu_time_per_frame

Revision             Result                    N
chromium@474300      0.175513 +- 0.170498      21      good
chromium@474499      0.170566 +- 0.153724      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.key_silk_cases

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

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


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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_other_cpu_time_per_frame/thread_other_cpu_time_per_frame

Revision             Result                    N
chromium@474300      0.175513 +- 0.170498      21      good
chromium@474499      0.170566 +- 0.153724      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.key_silk_cases

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

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


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

Bisect can't repro. This happened on one page and one device.