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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgi9PE8QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgy5iV5AsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgq6Cu4ggM


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

chromium-rel-mac-hdd
chromium-rel-mac10
chromium-rel-mac11

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

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

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


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

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@432013  40.1451  299.657  35  good
chromium@432080  43.955   322.338  35  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 666652

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.browsing_desktop_ignition
Test Metric: v8-gc-full-mark-compactor_max/v8-gc-full-mark-compactor_max
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/1036
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995673384489541024


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

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2482
Failure reason: the build has failed due to infrastructure failure.

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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: No values were found while testing the reference range.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@431847  N/A   N/A      0  good
chromium@432080  N/A   N/A      0  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 666652

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.browsing_desktop_ignition
Test Metric: v8-gc-scavenger_sum/browse_news
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2486
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995646780845631744


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

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

Looks infrastructure-related. Regressions occur when browse_social datapoints end.

hpayer@ PTAL.

Yes, that is very unfortunate. The global graph is heavily effected by disabling tests. Nothing actionable here. The tests should get re-enabled ASAP.

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: mac_10_10_perf_bisect
  Benchmark    : v8.browsing_desktop_ignition
  Metric       : v8-gc-scavenger_sum/browse_news


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

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

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


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