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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0K3ysQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0KSSswkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0KjMlQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkL-yrAoM


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

android-nexus7v2
chromium-rel-mac-retina

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : memory.long_running_idle_gmail_background_tbmv2
  Metric       : v8-gc-latency-mark-compactor_max/v8-gc-latency-mark-compactor_max

Revision             Result                  N
chromium@444328      93.0514 +- 163.719      21      good
chromium@444371      103.288 +- 110.841      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.long_running_idle_gmail_background_tbmv2

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

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


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

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