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

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


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

chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-mac12-mini-8gb
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
linux-release

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

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

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

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

Revision             Result                     N
chromium@504762      0.342191 +- 0.0347296      21      good
chromium@504839      0.342793 +- 0.0100074      21      bad

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


For feedback, file a bug with component Speed>Bisection

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

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/load_media/load_media_soundcloud

Revision             Result                  N
chromium@504734      986.257 +- 108.596      21      good
chromium@504807      985.907 +- 122.269      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.media.soundcloud 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/8965857551017814032


For feedback, file a bug with component Speed>Bisection

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

Could this be bimodal, or is the behavior that someone landed a change, reverted, and then re-landed quickly? If so, this might be difficult to find. We don't seem to have any ref builds for these as well, so I can't tell if this is real. If the next bisect fails, what can we do?

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : cpu_time_percentage_avg/browse_media/browse_media_flickr_infinite_scroll

Revision             Result                     N
chromium@504762      0.32419 +- 0.0336896       21      good
chromium@504839      0.325892 +- 0.0381888      21      bad

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.media.flickr.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/8964634541566755264


For feedback, file a bug with component Speed>Bisection

self-assigning to investigate

Juan: are you still planning on looking at this bug?

Sorry, no. Probably not.