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

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


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.mobile_infinite_scroll_tbmv2
  Metric       : v8-gc-scavenger_max/v8-gc-scavenger_max

Revision             Result                  N
chromium@442568      21.5804 +- 6.63326      21      good
chromium@442607      22.1246 +- 7.8095       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 v8.mobile_infinite_scroll_tbmv2

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

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


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

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

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.