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

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


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

android-nexus5X

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : storage.indexeddb_endure
  Metric       : vm_private_dirty_final_browser/vm_private_dirty_final_browser

Revision             Result                  N
chromium@447537      29434.2 +- 2255.42      21      good
chromium@447557      29259.3 +- 842.917      9       good
chromium@447567      29315.8 +- 1058.08      14      good
chromium@447573      29312.7 +- 1363.72      20      good
chromium@447575      29503.9 +- 1864.25      21      unknown
chromium@447577      30089.7 +- 3507.89      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 storage.indexeddb_endure

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

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


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

Graph recovered. Marking wontfix.

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