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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=0204362df9d7b19b298bb626b52e039f3c0977e22bf8ade8a2c8ba26089b6585


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

chromium-rel-win7-gpu-intel

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : cpu_time_percentage_avg/browse_tech/browse_tech_discourse_infinite_scroll


To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.tech.discourse.infinite.scroll system_health.common_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8974084755066709952


For feedback, file a bug with component Speed>Bisection

I wonder if this is the same bug as https://bugs.chromium.org/p/chromium/issues/detail?id=747500

I will try another bisect.

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

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

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : css_animation:power_avg/load_news/load_news_flipboard

Revision             Result                  N
chromium@485863      21.4791 +- 1.09457      21      good
chromium@486263      21.7404 +- 3.53491      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 --story-filter=load.news.flipboard system_health.common_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973134776554829584


For feedback, file a bug with component Speed>Bisection

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : idle:power_avg/load_chrome/load_chrome_blank


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=load.chrome.blank system_health.common_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973134887355786096


For feedback, file a bug with component Speed>Bisection

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

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : video_animation:power_avg/browse_news/browse_news_nytimes

Revision             Result                  N
chromium@485638      37.6701 +- 22.4744      10      good
chromium@486269      40.3147 +- 11.9532      8       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.nytimes system_health.common_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973134822007332064


For feedback, file a bug with component Speed>Bisection

Two graph patterns: 1. regression --> progression that balanced it out. 2. ref build also regressed. WontFix.