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

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


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : tracing.tracing_with_debug_overhead
  Metric       : trace_size_avg/trace_size_avg

Revision             Result                 N
chromium@460279      7651767 +- 914925      21      good
chromium@460329      7662871 +- 704886      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 tracing.tracing_with_debug_overhead

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

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


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

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