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

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


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

chromium-rel-mac11-pro

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

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : delphick
  Commit : c41d3c785c5179a38e54c6c80ea63d56cc7cfd12
  Date   : Fri Apr 28 11:50:09 2017
  Subject: Restore one millisecond minimum timeout for setTimeout.

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/browse_news/browse_news_flipboard
  Change       : 159.06% | 671.587166662 -> 1739.84716667

Revision             Result                  N
chromium@467929      671.587 +- 92.2744      6      good
chromium@467961      646.258 +- 45.2443      6      good
chromium@467962      1715.02 +- 128.064      6      bad       <--
chromium@467963      1706.19 +- 173.776      6      bad
chromium@467965      1657.83 +- 150.976      6      bad
chromium@467969      1780.01 +- 117.591      6      bad
chromium@467977      1747.54 +- 246.707      6      bad
chromium@467992      1739.85 +- 113.095      6      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 --story-filter=browse.news.flipboard system_health.common_desktop

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

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


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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : delphick
  Commit : c41d3c785c5179a38e54c6c80ea63d56cc7cfd12
  Date   : Fri Apr 28 11:50:09 2017
  Subject: Restore one millisecond minimum timeout for setTimeout.

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/browse_news/browse_news_flipboard
  Change       : 139.18% | 734.071333334 -> 1755.75683333

Revision             Result                  N
chromium@467929      734.071 +- 423.21       6      good
chromium@467961      669.782 +- 60.3181      6      good
chromium@467962      1728.75 +- 133.844      6      bad       <--
chromium@467963      1726.32 +- 136.522      6      bad
chromium@467965      1653.04 +- 229.976      6      bad
chromium@467969      1698.43 +- 220.262      6      bad
chromium@467977      1753.9 +- 148.789       6      bad
chromium@467992      1755.76 +- 137.478      6      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 --story-filter=browse.news.flipboard system_health.common_desktop

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

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


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