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

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


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

win-zenbook

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: 
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@438141  159.359  14.6353  30  good
chromium@438166  161.589  83.9051  30  unknown
chromium@438191  161.91   103.703  30  bad
chromium@438240  158.912  40.3637  30  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 675681

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.dom
Test Metric: modify-element-id/modify-element-id
Relative Change: 0.28%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/635
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8992819664477223552


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5774592486932480

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

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